From: syzbot <syzbot+a941018a091f1a1f9546@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, radoslaw.zielonek@gmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] INFO: rcu detected stall in validate_mm (3)
Date: Wed, 03 Jul 2024 01:21:03 -0700 [thread overview]
Message-ID: <000000000000d89405061c5382f2@google.com> (raw)
In-Reply-To: <20240703073158.643823-2-radoslaw.zielonek@gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
SYZFAIL: write(/proc/sys/fs/binfmt_misc/register) failed
2024/07/03 08:20:07 parsed 1 programs
2024/07/03 08:20:07 [FATAL] failed to run ["./syz-executor" "setup" "fault" "binfmt_misc" "usb" "802154" "swap"]: exit status 67
mkdir(/syzcgroup) failed: 17
mount(binfmt_misc) failed: 16
write(/proc/sys/fs/binfmt_misc/register) failed: 17
SYZFAIL: write(/proc/sys/fs/binfmt_misc/register) failed
(errno 17: File exists)
Tested on:
commit: dccb07f2 Merge tag 'for-6.9-rc7-tag' of git://git.kern..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=1657d115980000
kernel config: https://syzkaller.appspot.com/x/.config?x=7144b4fe7fbf5900
dashboard link: https://syzkaller.appspot.com/bug?extid=a941018a091f1a1f9546
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=10a5a915980000
next parent reply other threads:[~2024-07-03 8:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240703073158.643823-2-radoslaw.zielonek@gmail.com>
2024-07-03 8:21 ` syzbot [this message]
[not found] <20240703082413.649294-1-radoslaw.zielonek@gmail.com>
2024-07-03 9:06 ` [syzbot] [mm?] INFO: rcu detected stall in validate_mm (3) syzbot
2024-05-12 9:19 syzbot
2024-05-12 17:28 ` Liam R. Howlett
2024-05-12 20:41 ` Liam R. Howlett
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=000000000000d89405061c5382f2@google.com \
--to=syzbot+a941018a091f1a1f9546@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=radoslaw.zielonek@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.