From: syzbot <syzbot+7402e6c8042635c93ead@syzkaller.appspotmail.com>
To: 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, lorenzo.stoakes@oracle.com,
syzkaller-bugs@googlegroups.com, vbabka@suse.cz
Subject: Re: [syzbot] [mm?] [input?] [usb?] INFO: rcu detected stall in brk (2)
Date: Thu, 31 Oct 2024 09:41:02 -0700 [thread overview]
Message-ID: <6723b31e.050a0220.35b515.0165.GAE@google.com> (raw)
In-Reply-To: <c6b63e97-6839-4beb-bb94-e5914837a041@lucifer.local>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+7402e6c8042635c93ead@syzkaller.appspotmail.com
Tested-by: syzbot+7402e6c8042635c93ead@syzkaller.appspotmail.com
Tested on:
commit: cffcc47b mm/mlock: set the correct prev on failure
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git/ mm-hotfixes-unstable
console output: https://syzkaller.appspot.com/x/log.txt?x=1304a630580000
kernel config: https://syzkaller.appspot.com/x/.config?x=6648774f7c39d413
dashboard link: https://syzkaller.appspot.com/bug?extid=7402e6c8042635c93ead
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2024-10-31 16:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 16:03 [syzbot] [mm?] [input?] [usb?] INFO: rcu detected stall in brk (2) syzbot
2024-10-31 16:23 ` Lorenzo Stoakes
2024-10-31 16:41 ` syzbot [this message]
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
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=6723b31e.050a0220.35b515.0165.GAE@google.com \
--to=syzbot+7402e6c8042635c93ead@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--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=lorenzo.stoakes@oracle.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;
as well as URLs for NNTP newsgroup(s).