All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+e04e2c007ba2c80476cb@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [hams?] KASAN: slab-use-after-free Read in rose_get_neigh
Date: Wed, 25 Jun 2025 02:26:03 -0700	[thread overview]
Message-ID: <685bc0ab.a00a0220.2e5631.00c2.GAE@google.com> (raw)
In-Reply-To: <20250625082730.1756-1-hdanton@sina.com>

Hello,

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

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

Tested on:

commit:         7595b66a Merge tag 'selinux-pr-20250624' of git://git...
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14e0d182580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=4ec8b4e4d31ae914
dashboard link: https://syzkaller.appspot.com/bug?extid=e04e2c007ba2c80476cb
compiler:       Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
patch:          https://syzkaller.appspot.com/x/patch.diff?x=17775182580000

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

  reply	other threads:[~2025-06-25  9:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-11  6:56 [syzbot] [hams?] KASAN: slab-use-after-free Read in rose_get_neigh syzbot
2025-04-22  2:40 ` syzbot
2025-06-24 12:43   ` Kohei Enju
2025-06-24 13:20     ` syzbot
2025-06-25  5:44   ` Kohei Enju
2025-06-25  6:21     ` syzbot
2025-06-25  7:12   ` Hillf Danton
2025-06-25  7:31     ` syzbot
2025-06-25  8:27   ` Hillf Danton
2025-06-25  9:26     ` syzbot [this message]
2025-06-28 12:04   ` Kohei Enju
2025-06-28 13:22     ` 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=685bc0ab.a00a0220.2e5631.00c2.GAE@google.com \
    --to=syzbot+e04e2c007ba2c80476cb@syzkaller.appspotmail.com \
    --cc=hdanton@sina.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 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.