mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+5725792ce6a9938d1b24@syzkaller.appspotmail.com>
To: jeff@incrediblybased.co, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [acpica?] KASAN: use-after-free Read in acpi_ns_get_attached_object
Date: Tue, 27 Oct 2026 12:27:02 -0700	[thread overview]
Message-ID: <6ae0fb06.47d0a7c9.33355c.007d.GAE@google.com> (raw)
In-Reply-To: <CAGsrLdYA5DgGeuLpzEFot895T_N=gC1D6P65CVc8umDYb9Dy7Q@mail.gmail.com>

Hello,

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

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

Tested on:

commit:         62c45752 Merge tag 'vfs-7.4-rc1.keyring' of git://git...
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1521d53e580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=c4b7dc4693928b1
dashboard link: https://syzkaller.appspot.com/bug?extid=5725792ce6a9938d1b24
compiler:       gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
patch:          https://syzkaller.appspot.com/x/patch.diff?x=12bed53e580000

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

       reply	other threads:[~2026-10-27 19:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGsrLdYA5DgGeuLpzEFot895T_N=gC1D6P65CVc8umDYb9Dy7Q@mail.gmail.com>
2026-10-27 19:27 ` syzbot [this message]
     [not found] <CAGsrLdZs_9qUki=pESG8fMF+gOiQpiHm7GbqqHBumZ5BmNGG+Q@mail.gmail.com>
2026-10-27 19:08 ` syzbot
     [not found] <a9c47b19-08a0-4a8c-a9d7-30eb971e83ebn@googlegroups.com>
2026-07-29  5:52 ` syzbot
     [not found] <6c5210d5-3bc9-4ac9-b811-9fe3421f1747n@googlegroups.com>
2026-07-29  3:53 ` syzbot
2026-07-28  4:11 syzbot
2026-07-29  1:08 ` 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=6ae0fb06.47d0a7c9.33355c.007d.GAE@google.com \
    --to=syzbot+5725792ce6a9938d1b24@syzkaller.appspotmail.com \
    --cc=jeff@incrediblybased.co \
    --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

all inboxes | Powered by JetHome®