linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jann Horn <jannh@google.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: syzbot <syzbot+0ca979b86eaec7337a89@syzkaller.appspotmail.com>,
	 Liam.Howlett@oracle.com, akpm@linux-foundation.org,
	 linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linux-usb@vger.kernel.org,  syzkaller-bugs@googlegroups.com,
	vbabka@suse.cz,  Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [syzbot] [mm?] INFO: rcu detected stall in vms_complete_munmap_vmas
Date: Fri, 25 Oct 2024 17:20:52 +0200	[thread overview]
Message-ID: <CAG48ez3c=KS68hnLu26mw2qwkaT8__4cvFw8vdzK=R3QHv7XeQ@mail.gmail.com> (raw)
In-Reply-To: <832afb0c-98b7-4d29-8436-1ff6a65133b8@lucifer.local>

On Fri, Oct 25, 2024 at 1:37 PM Lorenzo Stoakes
<lorenzo.stoakes@oracle.com> wrote:
> On Fri, Oct 25, 2024 at 04:23:30AM -0700, syzbot wrote:
> > Hello,
> >
> > syzbot found the following issue on:
> >
> > HEAD commit:    c6d9e43954bf Merge 6.12-rc4 into usb-next
> > git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
> > console output: https://syzkaller.appspot.com/x/log.txt?x=139f225f980000
> > kernel config:  https://syzkaller.appspot.com/x/.config?x=4a2bb21f91d75c65
> > dashboard link: https://syzkaller.appspot.com/bug?extid=0ca979b86eaec7337a89
> > compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
> > syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=179f225f980000
> >
> > Downloadable assets:
> > disk image: https://storage.googleapis.com/syzbot-assets/3bf4a453ec2f/disk-c6d9e439.raw.xz
> > vmlinux: https://storage.googleapis.com/syzbot-assets/e4a2db2a5d95/vmlinux-c6d9e439.xz
> > kernel image: https://storage.googleapis.com/syzbot-assets/8eb8e481b288/bzImage-c6d9e439.xz
> >
> > IMPORTANT: if you fix the issue, please add the following tag to the commit:
> > Reported-by: syzbot+0ca979b86eaec7337a89@syzkaller.appspotmail.com
> >
>
> Isn't this just the same thing as [0]?
>
> Again I think we're just happening to hit a stall in the unmap logic rather than
> this being an mm thing.
>
> We retried that one a few times and it didn't hit any mm code after the
> first time.

Random side comment: It would be nice if the kernel was able to report
hangs in two steps; somehow scan and mark the stack in a first pass,
then wait another minute or so, then scan the stack again to see which
functions we haven't returned out of within that minute, or something
along those lines...


  parent reply	other threads:[~2024-10-25 15:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-25 11:23 syzbot
2024-10-25 11:37 ` Lorenzo Stoakes
2024-10-25 15:13   ` Alan Stern
2024-10-25 15:34     ` Lorenzo Stoakes
2024-10-25 15:20   ` Jann Horn [this message]
2024-10-25 15:46     ` Lorenzo Stoakes

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='CAG48ez3c=KS68hnLu26mw2qwkaT8__4cvFw8vdzK=R3QHv7XeQ@mail.gmail.com' \
    --to=jannh@google.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=syzbot+0ca979b86eaec7337a89@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