linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+885c03ad650731743489@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, asmadeus@codewreck.org,
	dhowells@redhat.com,  ericvh@kernel.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	 linux_oss@crudebyte.com, lucho@ionkov.net,
	syzkaller-bugs@googlegroups.com,  v9fs@lists.linux.dev
Subject: Re: [syzbot] [mm?] [v9fs?] BUG: stack guard page was hit in sys_open
Date: Mon, 09 Dec 2024 07:48:02 -0800	[thread overview]
Message-ID: <67571132.050a0220.2477f.004a.GAE@google.com> (raw)
In-Reply-To: <2132559.1733758162@warthog.procyon.org.uk>

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:         fac04efc Linux 6.13-rc2
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13ee54df980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=b041310d53c18b96
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=14f654df980000

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


      reply	other threads:[~2024-12-09 15:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6731d39c.050a0220.1fb99c.014e.GAE@google.com>
2024-11-17  1:38 ` 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 [this message]

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=67571132.050a0220.2477f.004a.GAE@google.com \
    --to=syzbot+885c03ad650731743489@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=asmadeus@codewreck.org \
    --cc=dhowells@redhat.com \
    --cc=ericvh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux_oss@crudebyte.com \
    --cc=lucho@ionkov.net \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=v9fs@lists.linux.dev \
    /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