From nobody Sun Jun 19 15:05:08 2022 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id D42CA874D4D for ; Sun, 19 Jun 2022 15:05:27 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ua1-x92a.google.com (mail-ua1-x92a.google.com [IPv6:2607:f8b0:4864:20::92a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4LQx0k43qCz4sVT for ; Sun, 19 Jun 2022 15:05:26 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-ua1-x92a.google.com with SMTP id n16so934341ual.12 for ; Sun, 19 Jun 2022 08:05:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=V9r8Ugp+syp3qNHjKIb8pTg6lNxiJlS+RmBnW4+Af8g=; b=1ShhwtR+d/nq5jNn2rLUx2obmwkcyiw0RwdwPPzj1PNqqbd/AIEDhU/IE82xu44qNp IhdDgcwV7ev1D6lQjGzPGtJT8ATTRP6isFSeuJJQ7oSGAGQEfQUKmsSP3EmAWdxK3d6+ grNu0sKw2i09b1ajfF2lgXyM9tjVkgrrfb4Cmx8aSJ7v8iBr0RRQZM1AlmLpq54LIhef cIkLQN+dcrbdglRb2X4RjU03ycRXvU7OH3tTGHKUMpO1iEfbH4mPe+Px/3I58i2w1/UN 1ytCkofgrJrU+s2glz+Bw7ohx+Tgj63g+axsRQ6wGfqKQOVeZlNDfHrbrY4bJO7B2VIc Mr7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=V9r8Ugp+syp3qNHjKIb8pTg6lNxiJlS+RmBnW4+Af8g=; b=NYFbY06tsVkODFCz8cXvQbisePiXZ13NzSVa+1MX4UopL2IdKgCzilMmynWOiELOj8 m+xK4PABs2jtbtYly/ZoHrI+UfkQs9ym73NXwQtrtLhtP9Jmu5ZIgyzHoSCXaKX/rUTJ i5ZyccwAZ4XVhKR1jvDPuC/EXatCae6w68qow2502BjH4fc+D59x4vjEigxvH8HZpWwq gLW1+zb4RTlx/1qXkuMyf93Zp9SXfZQE8kjyL9Y5lJk1396y/qyUErq/O5ANaE9AgTVF EH/ZtFJFOcbXBG0PeQnqgWnNZsEBGUmTE3J+biY50lnHVrfg/4k/t3jC+yFJxBQc9Woq IrIg== X-Gm-Message-State: AJIora8t29hTJsE20CPgkIizbAn2tKW2T7oP7tTmbANWYEd5Tgt02hW3 cMEFEDPm7fAt1/bO7YKjetND7+JY8QidH1b2fF7AuQ== X-Google-Smtp-Source: AGRyM1v0B+wj6FmMBC6JshIbgvj+ZcY07gA9nSyeBZ+3VRYpop4hgCY4LgKzK3y5jUPWDJoBjsICBLJVBuhULo3g85E= X-Received: by 2002:ab0:2a47:0:b0:37c:6868:2ec4 with SMTP id p7-20020ab02a47000000b0037c68682ec4mr6354707uar.48.1655651119314; Sun, 19 Jun 2022 08:05:19 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <20210520180155.3e23500e@bsd64.grem.de> <20210520185917.GL14975@funkthat.com> <20220619140624.21263e46@bsd64.grem.de> In-Reply-To: <20220619140624.21263e46@bsd64.grem.de> From: Warner Losh Date: Sun, 19 Jun 2022 09:05:08 -0600 Message-ID: Subject: Re: Reducing SIGINFO verbosity To: Michael Gmelin Cc: Ceri Davies , Conrad Meyer , "freebsd-current@freebsd.org" Content-Type: multipart/alternative; boundary="000000000000d6c9d005e1ce5087" X-Rspamd-Queue-Id: 4LQx0k43qCz4sVT X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20210112.gappssmtp.com header.s=20210112 header.b=1ShhwtR+; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::92a) smtp.mailfrom=wlosh@bsdimp.com X-Spamd-Result: default: False [-0.84 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20210112.gappssmtp.com:s=20210112]; NEURAL_HAM_MEDIUM(-0.32)[-0.325]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-0.999]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; NEURAL_SPAM_SHORT(0.48)[0.482]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20210112.gappssmtp.com:+]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::92a:from]; MLMMJ_DEST(0.00)[freebsd-current]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; R_SPF_NA(0.00)[no SPF record]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N --000000000000d6c9d005e1ce5087 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, Jun 19, 2022 at 6:06 AM Michael Gmelin wrote: > > > On Fri, 21 May 2021 08:36:49 -0600 > Warner Losh wrote: > > > On Fri, May 21, 2021 at 7:38 AM Ceri Davies > > wrote: > > > > > On Thu, May 20, 2021 at 03:57:17PM -0700, Conrad Meyer wrote: > > > > No, I don=E2=80=99t think there=E2=80=99s any reason to default it = differently on > > > > stable > > > vs > > > > current. I think it=E2=80=99s useful (and I prefer the more verbose= form, > > > > which isn=E2=80=99t the default). > > > > > > I agree that there's no reason for the default to be different, but > > > I would say that it is much easier for someone who knows that there > > > is a default to be changed to change it, than it is for someone who > > > does not. Therefore, if the information is not useful to someone > > > who does not know how to get rid of it, then it should default to > > > not being displayed, IMHO. > > > > > > > I plan on changing the default for non-INVARIANT kernels back to > > the old behavior. > > > > INVARIANT kernels will keep this behavior because it's a debugging > > kernel and this is one more thing to help debugging problems. > > > > Did this ever happen? I just installed a fresh 13.1-RELEASE production > system (non-INVARIANT kernel) and it seems like SIGINFO still outputs > kernel stack information. > I forgot before 13.1. Warner --000000000000d6c9d005e1ce5087 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Sun, Jun 19, 2022 at 6:06 AM Micha= el Gmelin <freebsd@grem.de> wr= ote:


On Fri, 21 May 2021 08:36:49 -0600
Warner Losh <imp@bsd= imp.com> wrote:

> On Fri, May 21, 2021 at 7:38 AM Ceri Davies <ceri@submonkey.net>
> wrote:
>
> > On Thu, May 20, 2021 at 03:57:17PM -0700, Conrad Meyer wrote:=C2= =A0
> > > No, I don=E2=80=99t think there=E2=80=99s any reason to defa= ult it differently on
> > > stable=C2=A0
> > vs=C2=A0
> > > current. I think it=E2=80=99s useful (and I prefer the more = verbose form,
> > > which isn=E2=80=99t the default).=C2=A0
> >
> > I agree that there's no reason for the default to be differen= t, but
> > I would say that it is much easier for someone who knows that the= re
> > is a default to be changed to change it, than it is for someone w= ho
> > does not. Therefore, if the information is not useful to someone<= br> > > who does not know how to get rid of it, then it should default to=
> > not being displayed, IMHO.
> >=C2=A0
>
> I plan on changing the default for non-INVARIANT kernels back to
> the old behavior.
>
> INVARIANT kernels will keep this behavior because it's a debugging=
> kernel and this is one more thing to help debugging problems.
>

Did this ever happen? I just installed a fresh 13.1-RELEASE production
system (non-INVARIANT kernel) and it seems like SIGINFO still outputs
kernel stack information.

I forgot befo= re 13.1.

Warner
--000000000000d6c9d005e1ce5087--