From: syzbot <syzbot+1f18c9b1bb51239d82f2@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, asmadeus@codewreck.org,
bharathsm@microsoft.com, brauner@kernel.org,
ceph-devel@vger.kernel.org, dhowells@redhat.com,
ericvh@kernel.org, idryomov@gmail.com, jlayton@kernel.org,
linux-afs@lists.infradead.org, linux-cifs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-trace-kernel@vger.kernel.org,
linux_oss@crudebyte.com, lucho@ionkov.net,
marc.dionne@auristor.com, mathieu.desnoyers@efficios.com,
mhiramat@kernel.org, netfs@lists.linux.dev, pc@manguebit.com,
ronniesahlberg@gmail.com, rostedt@goodmis.org,
samba-technical@lists.samba.org, sfrench@samba.org,
sprasad@microsoft.com, syzkaller-bugs@googlegroups.com,
tom@talpey.com, v9fs@lists.linux.dev, xiubli@redhat.com
Subject: Re: [syzbot] [mm?] [v9fs?] BUG: stack guard page was hit in sys_openat
Date: Fri, 21 Feb 2025 05:20:02 -0800 [thread overview]
Message-ID: <67b87d82.050a0220.14d86d.04d4.GAE@google.com> (raw)
In-Reply-To: <6792ffb7.050a0220.3ab881.0005.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit e2d46f2ec332533816417b60933954173f602121
Author: David Howells <dhowells@redhat.com>
Date: Mon Dec 16 20:41:17 2024 +0000
netfs: Change the read result collector to only use one work item
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15cb3ae4580000
start commit: 9528d418de4d Merge tag 'x86_urgent_for_v6.13' of git://git..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=d7f05e16f48c5834
dashboard link: https://syzkaller.appspot.com/bug?extid=1f18c9b1bb51239d82f2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17808824580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=129252b0580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: netfs: Change the read result collector to only use one work item
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
parent reply other threads:[~2025-02-21 13:20 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <6792ffb7.050a0220.3ab881.0005.GAE@google.com>]
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=67b87d82.050a0220.14d86d.04d4.GAE@google.com \
--to=syzbot+1f18c9b1bb51239d82f2@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=asmadeus@codewreck.org \
--cc=bharathsm@microsoft.com \
--cc=brauner@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=dhowells@redhat.com \
--cc=ericvh@kernel.org \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=marc.dionne@auristor.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=netfs@lists.linux.dev \
--cc=pc@manguebit.com \
--cc=ronniesahlberg@gmail.com \
--cc=rostedt@goodmis.org \
--cc=samba-technical@lists.samba.org \
--cc=sfrench@samba.org \
--cc=sprasad@microsoft.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tom@talpey.com \
--cc=v9fs@lists.linux.dev \
--cc=xiubli@redhat.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 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).