public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+2ff22910687ee0dfd48e@syzkaller.appspotmail.com>
To: andriy.shevchenko@linux.intel.com, dakr@kernel.org,
	djrscally@gmail.com,  gregkh@linuxfoundation.org,
	heikki.krogerus@linux.intel.com, jgg@nvidia.com,
	 kevin.tian@intel.com, linux-acpi@vger.kernel.org,
	 linux-kernel@vger.kernel.org, nicolinc@nvidia.com,
	rafael@kernel.org,  sakari.ailus@linux.intel.com,
	syzkaller-bugs@googlegroups.com,  yi.l.liu@intel.com
Subject: Re: [syzbot] [acpi?] KASAN: slab-use-after-free Read in software_node_notify_remove
Date: Sun, 06 Apr 2025 06:31:02 -0700	[thread overview]
Message-ID: <67f28216.050a0220.0a13.0269.GAE@google.com> (raw)
In-Reply-To: <Z_J94Up33luYw6Xg@smile.fi.intel.com>

Hello,

syzbot tried to test the proposed patch but the build/boot failed:

failed to checkout kernel repo git@bitbucket.org:andy-shev/linux.git/test-swnode: failed to run ["git" "fetch" "--force" "f7e55974102a831d64e9ca077790e9122f71f6c9" "test-swnode"]: exit status 128
Host key verification failed.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.



Tested on:

commit:         [unknown 
git tree:       git@bitbucket.org:andy-shev/linux.git test-swnode
kernel config:  https://syzkaller.appspot.com/x/.config?x=24f9c4330e7c0609
dashboard link: https://syzkaller.appspot.com/bug?extid=2ff22910687ee0dfd48e
compiler:       

Note: no patches were applied.

  reply	other threads:[~2025-04-06 13:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-06 11:37 [syzbot] [acpi?] KASAN: slab-use-after-free Read in software_node_notify_remove syzbot
2025-04-06 13:13 ` Andy Shevchenko
2025-04-06 13:31   ` syzbot [this message]
2025-04-06 13:24 ` Andy Shevchenko
2025-04-06 14:09   ` syzbot
2025-04-08 14:54 ` Andy Shevchenko
2025-04-10  0:57 ` [syzbot] " syzbot
2025-04-10 14:23 ` syzbot
2025-04-11  0:42 ` [PATCH] software node: Prevent link creation failure from causing kobj reference count imbalance Lizhi Xu
2025-04-14  6:20   ` Andy Shevchenko
2025-04-14  6:27     ` Andy Shevchenko
2025-04-14  7:08     ` Lizhi Xu
2025-04-14  7:16       ` Andy Shevchenko
2025-04-14  7:11     ` [PATCH V2] " Lizhi Xu
2025-04-14  7:22       ` Andy Shevchenko
2025-04-14  8:41       ` Sakari Ailus
     [not found] <20250410005712.2532007-1-lizhi.xu@windriver.com>
2025-04-10  4:43 ` [syzbot] [acpi?] KASAN: slab-use-after-free Read in software_node_notify_remove syzbot
     [not found] <20250410111546.3939-1-hdanton@sina.com>
2025-04-10 11:58 ` syzbot
     [not found] <20250410142307.164379-1-lizhi.xu@windriver.com>
2025-04-10 19:11 ` syzbot
     [not found] <20250415110145.4052-1-hdanton@sina.com>
2025-04-15 11:35 ` 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=67f28216.050a0220.0a13.0269.GAE@google.com \
    --to=syzbot+2ff22910687ee0dfd48e@syzkaller.appspotmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=dakr@kernel.org \
    --cc=djrscally@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=jgg@nvidia.com \
    --cc=kevin.tian@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolinc@nvidia.com \
    --cc=rafael@kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=yi.l.liu@intel.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