From: syzbot <syzbot+1fc6f64c40a9d143cfb6@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, lizhi.xu@windriver.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] BUG: stack guard page was hit in v9fs_file_read_iter
Date: Thu, 07 Nov 2024 01:53:03 -0800 [thread overview]
Message-ID: <672c8dff.050a0220.49393.0176.GAE@google.com> (raw)
In-Reply-To: <20241107093553.135565-1-lizhi.xu@windriver.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
kernel panic: corrupted stack end in corrupted
subreq: ffff88802e249680, 1async: 0, r: ffff888023be2d80, transed: 4096, sub req length: 16777088, retry times: 47, subreq consume: 0, subreq list empty: 0, netfs_read_subreq_terminated
subreq: ffff88802e249680, err: 0, total: 0, transfed: 4096, v9fs_issue_read
Kernel panic - not syncing: corrupted stack end detected inside scheduler
CPU: 1 UID: 0 PID: 19770 Comm: syz.0.14673 Not tainted 6.12.0-rc6-syzkaller-gff7afaeca1a1-dirty #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
Call Trace:
<TASK>
Tested on:
commit: ff7afaec Merge tag 'nfs-for-6.12-3' of git://git.linux..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1195bd5f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=c0b2fb415081f288
dashboard link: https://syzkaller.appspot.com/bug?extid=1fc6f64c40a9d143cfb6
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=17b00ea7980000
next parent reply other threads:[~2024-11-07 9:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241107093553.135565-1-lizhi.xu@windriver.com>
2024-11-07 9:53 ` syzbot [this message]
[not found] <20241108021849.2997512-1-lizhi.xu@windriver.com>
2024-11-08 2:36 ` [syzbot] [mm?] BUG: stack guard page was hit in v9fs_file_read_iter syzbot
[not found] <20241108014747.2901141-1-lizhi.xu@windriver.com>
2024-11-08 1:54 ` syzbot
[not found] <20241107055816.3307082-1-lizhi.xu@windriver.com>
2024-11-07 6:16 ` syzbot
[not found] <20241107041020.3067059-1-lizhi.xu@windriver.com>
2024-11-07 4:23 ` syzbot
[not found] <20241107031237.2751625-1-lizhi.xu@windriver.com>
2024-11-07 3:25 ` syzbot
2024-11-06 14:08 syzbot
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=672c8dff.050a0220.49393.0176.GAE@google.com \
--to=syzbot+1fc6f64c40a9d143cfb6@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.xu@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox