[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f908337e-a910-4f35-adc6-5c48f4a1bb99@lucifer.local>
Date: Fri, 1 Nov 2024 12:14:14 +0000
From: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
To: Aleksandr Nogikh <nogikh@...gle.com>
Cc: syzbot <syzbot+7402e6c8042635c93ead@...kaller.appspotmail.com>,
akpm@...ux-foundation.org, jannh@...gle.com, liam.howlett@...cle.com,
linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, linux-usb@...r.kernel.org,
syzkaller-bugs@...glegroups.com, vbabka@...e.cz,
Alan Stern <stern@...land.harvard.edu>,
Dmitry Vyukov <dvyukov@...gle.com>
Subject: Re: [syzbot] [mm?] [input?] [usb?] INFO: rcu detected stall in brk
(2)
On Fri, Nov 01, 2024 at 01:09:24PM +0100, Aleksandr Nogikh wrote:
> On Fri, Nov 1, 2024 at 12:11 PM Lorenzo Stoakes
> > Maybe worth setting CONFIG_RCU_EXP_CPU_STALL_TIMEOUT to 0 so it matches the CPU
> > stall timeout? At least for builds that also set heavy debug options like
> > CONFIG_DEBUG_VM_MAPLE_TREE?
>
> Oh, that's even simpler than I thought it would be, thank you!
> I've sent https://github.com/google/syzkaller/pull/5455, it will come
> into effect in a few days.
>
> --
> Aleksandr
>
Perfect, thanks very much!
Powered by blists - more mailing lists