public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+a0fa177e13690b663c74@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	 wojciech.gladysz@infogain.com
Subject: Re: [syzbot] [mm?] BUG: unable to handle kernel paging request in bpf_probe_read_kernel_str
Date: Wed, 19 Jun 2024 08:14:03 -0700	[thread overview]
Message-ID: <0000000000000f79f5061b3fa675@google.com> (raw)
In-Reply-To: <PN2PR01MB4891B0B970F2651B49799F14FCCF2@PN2PR01MB4891.INDPRD01.PROD.OUTLOOK.COM>

Hello,

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

Reported-and-tested-by: syzbot+a0fa177e13690b663c74@syzkaller.appspotmail.com

Tested on:

commit:         32019c65 x86/mm: Disallow vsyscall page read for copy_..
git tree:       https://linux.googlesource.com/linux/kernel/git/torvalds/linux
console output: https://syzkaller.appspot.com/x/log.txt?x=146e310e980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=5e23375d0c3afdc8
dashboard link: https://syzkaller.appspot.com/bug?extid=a0fa177e13690b663c74
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.

       reply	other threads:[~2024-06-19 15:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <PN2PR01MB4891B0B970F2651B49799F14FCCF2@PN2PR01MB4891.INDPRD01.PROD.OUTLOOK.COM>
2024-06-19 15:14 ` syzbot [this message]
     [not found] <PN2PR01MB4891B3CD4C11DCC8DDD854FAFCCF2@PN2PR01MB4891.INDPRD01.PROD.OUTLOOK.COM>
2024-06-19 14:50 ` [syzbot] [mm?] BUG: unable to handle kernel paging request in bpf_probe_read_kernel_str syzbot
2024-02-07  7:16 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=0000000000000f79f5061b3fa675@google.com \
    --to=syzbot+a0fa177e13690b663c74@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=wojciech.gladysz@infogain.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