From: syzbot <syzbot+a9391462075ffb9f77c6@syzkaller.appspotmail.com>
To: brauner@kernel.org, christian.koenig@amd.com,
dri-devel@lists.freedesktop.org, hch@infradead.org,
jack@suse.cz, jhubbard@nvidia.com, kees@kernel.org,
linaro-mm-sig@lists.linaro.org, linux-fsdevel@vger.kernel.org,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, linux-mm@kvack.org,
sumit.semwal@linaro.org, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [fs?] [mm?] WARNING in path_noexec (2)
Date: Sun, 02 Aug 2026 10:07:02 -0700 [thread overview]
Message-ID: <6a6f7936.13bfb6d0.1ecdd5.0272.GAE@google.com> (raw)
In-Reply-To: <68dc3ade.a70a0220.10c4b.015b.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit 6de2aeffabaafaeda819e60ec8d04f199711e11a
Author: John Hubbard <jhubbard@nvidia.com>
Date: Thu Jun 4 02:53:14 2026 +0000
libfs: set SB_I_NOEXEC and SB_I_NODEV by default in init_pseudo()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11c53db9580000
start commit: ba3e43a9e601 Merge tag 'soc-fixes-7.1-2' of git://git.kern..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=65472e27d1590a04
dashboard link: https://syzkaller.appspot.com/bug?extid=a9391462075ffb9f77c6
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12a08f2e580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1697af2e580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: libfs: set SB_I_NOEXEC and SB_I_NODEV by default in init_pseudo()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2026-08-02 17:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 20:17 [syzbot] [fs?] [mm?] WARNING in path_noexec (2) syzbot
2025-09-30 22:04 ` Kees Cook
2025-10-06 10:47 ` Christian Brauner
2026-08-02 17:07 ` syzbot [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=6a6f7936.13bfb6d0.1ecdd5.0272.GAE@google.com \
--to=syzbot+a9391462075ffb9f77c6@syzkaller.appspotmail.com \
--cc=brauner@kernel.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=jhubbard@nvidia.com \
--cc=kees@kernel.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sumit.semwal@linaro.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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