From: syzbot <syzbot+3de83a9efcca3f0412ee@syzkaller.appspotmail.com>
To: axboe@kernel.dk, brauner@kernel.org, jack@suse.cz,
kees@kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [mm?] [fs?] WARNING in path_noexec
Date: Mon, 07 Jul 2025 05:10:03 -0700 [thread overview]
Message-ID: <686bb91b.a00a0220.c7b3.0085.GAE@google.com> (raw)
In-Reply-To: <20250707-tusche-umlaufen-6e96566552d6@brauner>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+3de83a9efcca3f0412ee@syzkaller.appspotmail.com
Tested-by: syzbot+3de83a9efcca3f0412ee@syzkaller.appspotmail.com
Tested on:
commit: 98f99394 secretmem: use SB_I_NOEXEC
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git vfs.fixes
console output: https://syzkaller.appspot.com/x/log.txt?x=13829f70580000
kernel config: https://syzkaller.appspot.com/x/.config?x=8211a357c817ddc6
dashboard link: https://syzkaller.appspot.com/bug?extid=3de83a9efcca3f0412ee
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-07-07 12:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 11:02 syzbot
2025-07-07 11:30 ` Christian Brauner
2025-07-07 12:10 ` syzbot [this message]
2025-07-07 12:10 ` [PATCH] secretmem: use SB_I_NOEXEC Christian Brauner
2025-07-07 12:32 ` Mike Rapoport
2025-07-07 17:17 ` Al Viro
2025-07-08 7:38 ` Christian Brauner
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=686bb91b.a00a0220.c7b3.0085.GAE@google.com \
--to=syzbot+3de83a9efcca3f0412ee@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=kees@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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