All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+bdb4bd87b5e22058e2a4@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	 xiyou.wangcong@gmail.com
Subject: Re: [syzbot] [net?] [virt?] BUG: stack guard page was hit in vsock_bpf_recvmsg
Date: Sun, 11 Aug 2024 19:18:03 -0700	[thread overview]
Message-ID: <000000000000592189061f731a66@google.com> (raw)
In-Reply-To: <CAM_iQpUTMQvq9Z7tM1upFGpKMWoc8FcftwREsy1SyTfHNv2cTw@mail.gmail.com>

Hello,

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

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

Tested on:

commit:         c4e82c02 net: dsa: microchip: ksz9477: split half-dupl..
git tree:       net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=108d3f23980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=e8a2eef9745ade09
dashboard link: https://syzkaller.appspot.com/bug?extid=bdb4bd87b5e22058e2a4
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=1792e95d980000

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

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAM_iQpUTMQvq9Z7tM1upFGpKMWoc8FcftwREsy1SyTfHNv2cTw@mail.gmail.com>
2024-08-12  2:18 ` syzbot [this message]
     [not found] <CAM_iQpV6aNoiXkYejbgfeQQpwL5LsE9rtJdOdjeRrnQyRuR19Q@mail.gmail.com>
2024-08-12  1:37 ` [syzbot] [net?] [virt?] BUG: stack guard page was hit in vsock_bpf_recvmsg syzbot
2024-08-09 17:42 syzbot
2024-08-10 12:07 ` syzbot
2024-08-11  0:13 ` Hillf Danton
2024-08-11  0:46   ` 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=000000000000592189061f731a66@google.com \
    --to=syzbot+bdb4bd87b5e22058e2a4@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=xiyou.wangcong@gmail.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.