All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+885c03ad650731743489@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, lizhi.xu@windriver.com,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] [v9fs?] BUG: stack guard page was hit in sys_open
Date: Sun, 17 Nov 2024 18:11:03 -0800	[thread overview]
Message-ID: <673aa237.050a0220.87769.001b.GAE@google.com> (raw)
In-Reply-To: <20241118015156.3320638-1-lizhi.xu@windriver.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-by: syzbot+885c03ad650731743489@syzkaller.appspotmail.com
Tested-by: syzbot+885c03ad650731743489@syzkaller.appspotmail.com

Tested on:

commit:         adc21867 Linux 6.12
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15cf32e8580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=55f8591b98dd132
dashboard link: https://syzkaller.appspot.com/bug?extid=885c03ad650731743489
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=15ae3b5f980000

Note: testing is done by a robot and is best-effort only.

       reply	other threads:[~2024-11-18  2:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241118015156.3320638-1-lizhi.xu@windriver.com>
2024-11-18  2:11 ` syzbot [this message]
2024-11-11  9:51 [syzbot] [v9fs?] BUG: stack guard page was hit in sys_open syzbot
2024-11-17  1:38 ` [syzbot] [mm?] " syzbot
2024-11-17  1:45   ` asmadeus
2024-11-18 16:23   ` David Howells
2024-11-18 16:36     ` syzbot
2024-11-18 17:23   ` David Howells
2024-11-18 17:41     ` syzbot
2024-12-09 15:06   ` David Howells
2024-12-09 15:07     ` syzbot
2024-12-09 15:29   ` David Howells
2024-12-09 15:48     ` 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=673aa237.050a0220.87769.001b.GAE@google.com \
    --to=syzbot+885c03ad650731743489@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.