public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Carlos Llamas <cmllamas@google.com>
To: syzbot <syzbot+7015dcf45953112c8b45@syzkaller.appspotmail.com>
Cc: arve@android.com, brauner@kernel.org, gregkh@linuxfoundation.org,
	joel@joelfernandes.org, linux-kernel@vger.kernel.org,
	linux-next@vger.kernel.org, maco@android.com,
	sfr@canb.auug.org.au, surenb@google.com,
	syzkaller-bugs@googlegroups.com, tkjos@android.com
Subject: Re: [syzbot] [kernel?] linux-next test error: KASAN: slab-use-after-free Write in binder_add_device
Date: Fri, 24 Jan 2025 00:11:24 +0000	[thread overview]
Message-ID: <Z5LarLkj50YumVD1@google.com> (raw)
In-Reply-To: <6792a5db.050a0220.3ab881.0002.GAE@google.com>

On Thu, Jan 23, 2025 at 12:26:03PM -0800, syzbot wrote:
> Hello,
> 
> syzbot tried to test the proposed patch but the build/boot failed:
> 
> 0][   T52]  ieee80211_unregister_hw+0x5d/0x2c0
> [   72.827744][   T52]  mac80211_hwsim_del_radio+0x2c4/0x4c0
> [   72.827761][   T52]  ? __pfx_mac80211_hwsim_del_radio+0x10/0x10
> [   72.827777][   T52]  hwsim_exit_net+0x5c1/0x670
> [   72.827790][   T52]  ? __pfx_hwsim_exit_net+0x10/0x10
> [   72.827802][   T52]  ? __ip_vs_dev_cleanup_batch+0x239/0x260
> [   72.827818][   T52]  cleanup_net+0x812/0xd60
> [   72.827831][   T52]  ? __pfx_cleanup_net+0x10/0x10
> [   72.827847][   T52]  ? process_scheduled_works+0x976/0x1840
> [   72.827861][   T52]  process_scheduled_works+0xa66/0x1840
> [   72.827882][   T52]  ? __pfx_process_scheduled_works+0x10/0x10
> [   72.827898][   T52]  ? assign_work+0x364/0x3d0
> [   72.827913][   T52]  worker_thread+0x870/0xd30
> [   72.827931][   T52]  ? __kthread_parkme+0x169/0x1d0
> [   72.827946][   T52]  ? __pfx_worker_thread+0x10/0x10
> [   72.827960][   T52]  kthread+0x7a9/0x920
> [   72.827975][   T52]  ? __pfx_kthread+0x10/0x10
> [   72.827991][   T52]  ? __pfx_worker_thread+0x10/0x10
> [   72.828004][   T52]  ? __pfx_kthread+0x10/0x10
> [   72.828019][   T52]  ? __pfx_kthread+0x10/0x10
> [   72.828035][   T52]  ? __pfx_kthread+0x10/0x10
> [   72.828057][   T52]  ? _raw_spin_unlock_irq+0x23/0x50
> [   72.828073][   T52]  ? lockdep_hardirqs_on+0x99/0x150
> [   72.828083][   T52]  ? __pfx_kthread+0x10/0x10
> [   72.828099][   T52]  ret_from_fork+0x4b/0x80
> [   72.828115][   T52]  ? __pfx_kthread+0x10/0x10
> [   72.828130][   T52]  ret_from_fork_asm+0x1a/0x30
> [   72.828147][   T52]  </TASK>

Huh? it sounds like linux-next is broken right now. This is some
unrelated lockdep issue. Let me retry with char-misc tree instead.

  reply	other threads:[~2025-01-24  0:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-16 11:08 [syzbot] [kernel?] linux-next test error: KASAN: slab-use-after-free Write in binder_add_device syzbot
2025-01-23 12:32 ` Aleksandr Nogikh
2025-01-23 16:49   ` Carlos Llamas
2025-01-27 18:50     ` Aleksandr Nogikh
2025-01-23 19:06 ` Carlos Llamas
2025-01-23 20:26   ` syzbot
2025-01-24  0:11     ` Carlos Llamas [this message]
2025-01-24  0:20 ` Carlos Llamas
2025-01-24  1:05   ` 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=Z5LarLkj50YumVD1@google.com \
    --to=cmllamas@google.com \
    --cc=arve@android.com \
    --cc=brauner@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=joel@joelfernandes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=maco@android.com \
    --cc=sfr@canb.auug.org.au \
    --cc=surenb@google.com \
    --cc=syzbot+7015dcf45953112c8b45@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tkjos@android.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