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 18:36:02 -0800 [thread overview]
Message-ID: <672d7912.050a0220.0db4.01b9.GAE@google.com> (raw)
In-Reply-To: <20241108021849.2997512-1-lizhi.xu@windriver.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+1fc6f64c40a9d143cfb6@syzkaller.appspotmail.com
Tested-by: syzbot+1fc6f64c40a9d143cfb6@syzkaller.appspotmail.com
Tested on:
commit: 906bd684 Merge tag 'spi-fix-v6.12-rc6' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=162d6e30580000
kernel config: https://syzkaller.appspot.com/x/.config?x=20d60fe605153ebe
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=108bfd5f980000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2024-11-08 2:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241108021849.2997512-1-lizhi.xu@windriver.com>
2024-11-08 2:36 ` syzbot [this message]
[not found] <20241108014747.2901141-1-lizhi.xu@windriver.com>
2024-11-08 1:54 ` [syzbot] [mm?] BUG: stack guard page was hit in v9fs_file_read_iter syzbot
[not found] <20241107093553.135565-1-lizhi.xu@windriver.com>
2024-11-07 9:53 ` 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=672d7912.050a0220.0db4.01b9.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 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.