public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+cc32304f6487ebff9b70@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bpf?] KASAN: slab-out-of-bounds Read in btf_datasec_check_meta
Date: Mon, 11 Mar 2024 06:07:04 -0700	[thread overview]
Message-ID: <000000000000cf7095061362372b@google.com> (raw)
In-Reply-To: <tencent_7B6E46C35367636DE97C83A16448F7623705@qq.com>

Hello,

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

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

Tested on:

commit:         afe0cbf2 mm: Introduce vmap_page_range() to map pages ..
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=15dad8d6180000
kernel config:  https://syzkaller.appspot.com/x/.config?x=92e06b597766606e
dashboard link: https://syzkaller.appspot.com/bug?extid=cc32304f6487ebff9b70
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=1002c63e180000

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

  reply	other threads:[~2024-03-11 13:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-11  8:55 [syzbot] [bpf?] KASAN: slab-out-of-bounds Read in btf_datasec_check_meta syzbot
2024-03-11 12:44 ` Edward Adam Davis
2024-03-11 13:07   ` syzbot [this message]
2024-03-11 13:16 ` [PATCH bpf-next] bpf: fix oob in btf_name_valid_section Edward Adam Davis
2024-03-11 14:48   ` Eduard Zingerman
2024-03-11 18:01     ` Andrii Nakryiko
2024-03-11 18:28       ` Eduard Zingerman

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=000000000000cf7095061362372b@google.com \
    --to=syzbot+cc32304f6487ebff9b70@syzkaller.appspotmail.com \
    --cc=eadavis@qq.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox