From: Dmitry Vyukov <firstname.lastname@example.org> To: Guilherme Piccoli <email@example.com> Cc: Tetsuo Handa <firstname.lastname@example.org>, LKML <email@example.com>, syzkaller <firstname.lastname@example.org>, email@example.com, CKI Project <firstname.lastname@example.org>, kbuild test robot <email@example.com>, firstname.lastname@example.org Subject: Re: [PATCH V3] kernel/hung_task.c: Introduce sysctl to print all traces when a hung task is detected Date: Mon, 30 Mar 2020 10:49:03 +0200 Message-ID: <CACT4Y+bjsEFsP1ELGuTXbZV5m3gWys444p5cq=375KPkpFk0Gg@mail.gmail.com> (raw) In-Reply-To: <CAHD1Q_zx29ZP37WcUr34ZEyqWkA9J23RmLa8jFyuLDrS_yC50A@mail.gmail.com> On Mon, Mar 30, 2020 at 2:43 AM Guilherme Piccoli <email@example.com> wrote: > > Hi Tetsuo and Dmitry, thanks for noticing this Tetsuo. And sorry for > not looping you in the patch Dmitry, I wasn't aware that you were > working with testing. By the way, I suggest people interested in linux > testing to create a ML; I'd be glad to have looped such list, but I > couldn't find information about a group dealing with testing. > > So Tetsuo, you got it right: just change it to > "sysctl.kernel.hung_task_all_cpu_backtrace=1" and that should work > fine, once Vlastimil's patch gets merged (and I hope it happens soon). > Cheers, > > > Guilherme +LKML, workflows, syzkaller, kernelci, cki, kbuild Tetsuo, thanks for notifying again. Yes, kernel devs breaking all testing happens from time to time and currently there is no good way to address this. Other things I remember is the introduction of CONFIG_DEBUG_MEMORY, which defaults to =n and disables KASAN, which in turn produced an explosion of assorted crashes caused by memory corruptions; also periodic changes in kernel crash messages which I assume all testing systems parse and need to understand. Is there already a mailing list for this? Or should we create one? I.e. announce and changes that may need actions from all testing systems. Another thing that may benefit from announcements is addition of new useful debugging configs. Currently they are introduced silently and don't reach the target audience.
next parent reply index Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <firstname.lastname@example.org> [not found] ` <email@example.com> [not found] ` <CAHD1Q_zx29ZP37WcUr34ZEyqWkA9J23RmLa8jFyuLDrS_yC50A@mail.gmail.com> 2020-03-30 8:49 ` Dmitry Vyukov [this message] 2020-03-30 9:01 ` Dmitry Vyukov 2020-03-30 11:57 ` Tetsuo Handa
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CACT4Y+bjsEFsP1ELGuTXbZV5m3gWys444p5cq=375KPkpFk0Gg@mail.gmail.com' \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Workflows Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/workflows/0 workflows/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 workflows workflows/ https://lore.kernel.org/workflows \ email@example.com public-inbox-index workflows Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.workflows AGPL code for this site: git clone https://public-inbox.org/public-inbox.git