From nobody Thu Jun 23 17:15:55 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 41D2186C00D for ; Thu, 23 Jun 2022 17:16:08 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-vs1-xe29.google.com (mail-vs1-xe29.google.com [IPv6:2607:f8b0:4864:20::e29]) (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 4LTRjg3kSbz3CPS for ; Thu, 23 Jun 2022 17:16:07 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-vs1-xe29.google.com with SMTP id j1so11192368vsj.12 for ; Thu, 23 Jun 2022 10:16:07 -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=Ie7zC05vlqwgQSXWE+vtDFnw9TA9QsJXS/uEpOOx3B8=; b=Kw/Kgu9xizSNvUArgVq7zMQAWBiA2eN8dO4Mu46uakLGF/9kd2ZmIdeZ/Z4lA82teE 8CLf4ZUmW9lKn6jgFeEx6jtVzYzaVyTlOA/FPx3WyEmniMp5LlKJ3WHWZsyvw2VLfZql 4wrbyBp6AtbT/UyE3xo/NTY6O7lWajHsclidfR+MBBex3RBPm32HtEmT7g7BroxkBOhA iLtQ+EIegRsl1LDM49fw2nQQHf0X9jHzDkyHjOgYhJPsxzHxuVWj9uf9XX+VHiGc+e1I f0JK1D2jsptMlEAj7tsSpRJB1zebEfVLzJ8NNacIQLXWLJSqwqwUTccjvPS+v3q5ep1y H0JQ== 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=Ie7zC05vlqwgQSXWE+vtDFnw9TA9QsJXS/uEpOOx3B8=; b=12lXxPPjLPfeGEF+pAlNdaV8FZBkHz1C4DxbYXY8+v+Mlcbibdvafer/pxNsWs4JlB fcd6zjq8SR1H1fMrMLz0hNUjrGqmChtKyInDcOBzskaYQeFe3g/uUGDXIjYwhtF9tlgN KCGfya5jL/v4T8t5cmzVF7t5z8xCpupzQnDx8FaOYOQPO617sOwS1q6HKrUUXFtbWvLu aLrIanfvRnrY3vzzcIGlebAhWtCgWsG0e9V82+lCmIEvaAZ8YmTPWKLfkypF4q0pnNrk 73nIM2WuL0A6W7x55jWk01Wq1Wv0I+ChjU+2QhQuOb7hIjUAdUoSwfEtQ6U0lyAcnghF 7oFg== X-Gm-Message-State: AJIora919exMLuquocvWa25E9Gb/GchPPXANfCgnsuidd5JpA9rFNTqy xtrq4cO5q4xWJMrtlOftV/OxQxK6l/uKf/q1E+Mf36e1pc6XQQ== X-Google-Smtp-Source: AGRyM1tco8fs3BZV0Xk1ti2EKvr7KnRUe+lwdO9xGV9MJ7linBoQ5XR9g4FFoPOUZ/w2jviJYZ4PVnG/kT94h2xAw+k= X-Received: by 2002:a67:fbd3:0:b0:354:2f5b:6477 with SMTP id o19-20020a67fbd3000000b003542f5b6477mr11173113vsr.76.1656004566808; Thu, 23 Jun 2022 10:16:06 -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: Thu, 23 Jun 2022 11:15:55 -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="000000000000f3b27405e2209bed" X-Rspamd-Queue-Id: 4LTRjg3kSbz3CPS X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20210112.gappssmtp.com header.s=20210112 header.b="Kw/Kgu9x"; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::e29) smtp.mailfrom=wlosh@bsdimp.com X-Spamd-Result: default: False [-3.00 / 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(-1.00)[-0.999]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20210112.gappssmtp.com:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::e29: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 --000000000000f3b27405e2209bed 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. > https://reviews.freebsd.org/D35576 for those who wish to weigh in. Warner > Cheers > Michael > > -- > Michael Gmelin > --000000000000f3b27405e2209bed 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.

https://reviews.freebsd.org/D35576 fo= r those who wish to weigh in.

Warner
=C2=A0
Cheers
Michael

--
Michael Gmelin
--000000000000f3b27405e2209bed--