Date: Wed, 19 Apr 2023 13:39:49 -0600 From: Warner Losh <imp@bsdimp.com> To: Michael Gmelin <freebsd@grem.de> Cc: Ceri Davies <ceri@submonkey.net>, Conrad Meyer <cem@freebsd.org>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: Reducing SIGINFO verbosity Message-ID: <CANCZdfq9fAJGrYOf-8-XWrZRyw6oQGWQ47vB7AeeOVO7f9DtsQ@mail.gmail.com> In-Reply-To: <20230418123557.443cd189@bsd64.grem.de> References: <20210520180155.3e23500e@bsd64.grem.de> <20210520185917.GL14975@funkthat.com> <CAG6CVpWpDYid9F0fSWyyFVuh6SuNmV4HwEBQUKTCXDGfq6KwAw@mail.gmail.com> <YKe3coCxotoKBV0T@submonkey.net> <CANCZdfoJPB=-WMqH_Hd5ggGmY4GR2L7RJZpa_e9a2_ym5R4ZZA@mail.gmail.com> <20220619140624.21263e46@bsd64.grem.de> <CANCZdfpEP4SUGTE9LAOiEyEPaHps-b8a0v81yG-PK4skV37tPA@mail.gmail.com> <20230418123557.443cd189@bsd64.grem.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--000000000000f7229305f9b5969d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Doh! Slipped through the cracks... Building test kernel now and will push if it succeeds and boots. Warner On Tue, Apr 18, 2023 at 4:36=E2=80=AFAM Michael Gmelin <freebsd@grem.de> wr= ote: > > > On Thu, 23 Jun 2022 11:15:55 -0600 > Warner Losh <imp@bsdimp.com> wrote: > > > On Sun, Jun 19, 2022 at 6:06 AM Michael Gmelin <freebsd@grem.de> > > wrote: > > > > > > > > > > > On Fri, 21 May 2021 08:36:49 -0600 > > > Warner Losh <imp@bsdimp.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: > > > > > > 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 ver= bose > > > > > > 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 > > > > > > Hi Warner, > > I just installed 13.2-RELEASE, seems like this was never MFCd (it is in > main, but not in stable/13 or releng/13.2). TBH, I could've checked > myself back then (it's so easy to forget to MFC). > > Cheers > Michael > > p.s. Learned about it by hitting ctrl-t to check if freebsd-update on my > slow test machine is actually alive :D > > -- > Michael Gmelin > --000000000000f7229305f9b5969d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Doh! Slipped through=C2=A0the cracks...=C2=A0<div><br></di= v><div>Building test kernel now and will push if it succeeds and boots.</di= v><div><br></div><div>Warner</div></div><br><div class=3D"gmail_quote"><div= dir=3D"ltr" class=3D"gmail_attr">On Tue, Apr 18, 2023 at 4:36=E2=80=AFAM M= ichael Gmelin <<a href=3D"mailto:freebsd@grem.de">freebsd@grem.de</a>>= ; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px= 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br> <br> On Thu, 23 Jun 2022 11:15:55 -0600<br> Warner Losh <<a href=3D"mailto:imp@bsdimp.com" target=3D"_blank">imp@bsd= imp.com</a>> wrote:<br> <br> > On Sun, Jun 19, 2022 at 6:06 AM Michael Gmelin <<a href=3D"mailto:f= reebsd@grem.de" target=3D"_blank">freebsd@grem.de</a>><br> > wrote:<br> > <br> > ><br> > ><br> > > On Fri, 21 May 2021 08:36:49 -0600<br> > > Warner Losh <<a href=3D"mailto:imp@bsdimp.com" target=3D"_blan= k">imp@bsdimp.com</a>> wrote:<br> > >=C2=A0 <br> > > > On Fri, May 21, 2021 at 7:38 AM Ceri Davies <<a href=3D"m= ailto:ceri@submonkey.net" target=3D"_blank">ceri@submonkey.net</a>><br> > > > wrote:<br> > > >=C2=A0 <br> > > > > On Thu, May 20, 2021 at 03:57:17PM -0700, Conrad Meyer = wrote:=C2=A0 <br> > > > > > No, I don=E2=80=99t think there=E2=80=99s any reas= on to default it<br> > > > > > differently on stable=C2=A0 <br> > > > > vs=C2=A0 <br> > > > > > current. I think it=E2=80=99s useful (and I prefer= the more verbose<br> > > > > > form, which isn=E2=80=99t the default).=C2=A0 <br> > > > ><br> > > > > I agree that there's no reason for the default to b= e different,<br> > > > > but I would say that it is much easier for someone who = knows<br> > > > > that there is a default to be changed to change it, tha= n it is<br> > > > > for someone who does not. Therefore, if the information= is not<br> > > > > useful to someone who does not know how to get rid of i= t, then<br> > > > > it should default to not being displayed, IMHO.<br> > > > >=C2=A0 <br> > > ><br> > > > I plan on changing the default for non-INVARIANT kernels bac= k to<br> > > > the old behavior.<br> > > ><br> > > > INVARIANT kernels will keep this behavior because it's a= debugging<br> > > > kernel and this is one more thing to help debugging problems= .<br> > > >=C2=A0 <br> > ><br> > > Did this ever happen? I just installed a fresh 13.1-RELEASE<br> > > production system (non-INVARIANT kernel) and it seems like SIGINF= O<br> > > still outputs kernel stack information.<br> > >=C2=A0 <br> > <br> > <a href=3D"https://reviews.freebsd.org/D35576" rel=3D"noreferrer" targ= et=3D"_blank">https://reviews.freebsd.org/D35576</a>; for those who wish to = weigh in.<br> > <br> > Warner<br> > <br> > <br> <br> Hi Warner,<br> <br> I just installed 13.2-RELEASE, seems like this was never MFCd (it is in<br> main, but not in stable/13 or releng/13.2). TBH, I could've checked<br> myself back then (it's so easy to forget to MFC).<br> <br> Cheers<br> Michael<br> <br> p.s. Learned about it by hitting ctrl-t to check if freebsd-update on my<br= > slow test machine is actually alive :D<br> <br> -- <br> Michael Gmelin<br> </blockquote></div> --000000000000f7229305f9b5969d--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfq9fAJGrYOf-8-XWrZRyw6oQGWQ47vB7AeeOVO7f9DtsQ>