linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Aleksandr Nogikh <nogikh@google.com>
Cc: syzbot <syzbot+7402e6c8042635c93ead@syzkaller.appspotmail.com>,
	akpm@linux-foundation.org, jannh@google.com,
	liam.howlett@oracle.com, linux-input@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linux-usb@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	vbabka@suse.cz, Alan Stern <stern@rowland.harvard.edu>,
	Dmitry Vyukov <dvyukov@google.com>
Subject: Re: [syzbot] [mm?] [input?] [usb?] INFO: rcu detected stall in brk (2)
Date: Fri, 1 Nov 2024 12:14:14 +0000	[thread overview]
Message-ID: <f908337e-a910-4f35-adc6-5c48f4a1bb99@lucifer.local> (raw)
In-Reply-To: <CANp29Y58o0O8jTSP_SpBLVp7VK0bM4Svo7jBNZgDpv=s1DWJqQ@mail.gmail.com>

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!


      reply	other threads:[~2024-11-01 12:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-31 16:03 syzbot
2024-10-31 16:23 ` Lorenzo Stoakes
2024-10-31 16:41   ` syzbot
2024-10-31 16:58     ` Lorenzo Stoakes
2024-10-31 19:24       ` Alan Stern
2024-11-01 11:07         ` Lorenzo Stoakes
2024-11-01 11:02       ` Aleksandr Nogikh
2024-11-01 11:11         ` Lorenzo Stoakes
2024-11-01 12:09           ` Aleksandr Nogikh
2024-11-01 12:14             ` Lorenzo Stoakes [this message]

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=f908337e-a910-4f35-adc6-5c48f4a1bb99@lucifer.local \
    --to=lorenzo.stoakes@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=dvyukov@google.com \
    --cc=jannh@google.com \
    --cc=liam.howlett@oracle.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=nogikh@google.com \
    --cc=stern@rowland.harvard.edu \
    --cc=syzbot+7402e6c8042635c93ead@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=vbabka@suse.cz \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox