public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+3609b9b48e68e1fe47fd@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	 youjingxiaogao2@gmail.com
Subject: Re: [syzbot] [bluetooth?] KASAN: slab-use-after-free Write in hci_conn_drop (3)
Date: Sun, 08 Feb 2026 12:31:03 -0800	[thread overview]
Message-ID: <6988f287.050a0220.3b3015.005f.GAE@google.com> (raw)
In-Reply-To: <CAKZCeSX=JVK5OK0GLYry4gkEH9cryp-FG8k9WcR_6FsPsZR6JQ@mail.gmail.com>

Hello,

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

failed to apply patch:
checking file net/bluetooth/hci_conn.c
Hunk #1 succeeded at 1232 with fuzz 1.
checking file net/bluetooth/hci_sync.c
patch: **** unexpected end of file in patch



Tested on:

commit:         9845cf73 Add linux-next specific files for 20260205
git tree:       linux-next
kernel config:  https://syzkaller.appspot.com/x/.config?x=6336d8e94a7c517d
dashboard link: https://syzkaller.appspot.com/bug?extid=3609b9b48e68e1fe47fd
compiler:       
patch:          https://syzkaller.appspot.com/x/patch.diff?x=1038eb22580000


  parent reply	other threads:[~2026-02-08 20:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAKZCeSX=JVK5OK0GLYry4gkEH9cryp-FG8k9WcR_6FsPsZR6JQ@mail.gmail.com>
2026-02-08 20:03 ` #syz test syzbot
2026-02-08 20:09   ` kawada
2026-02-08 20:57     ` [syzbot] [bluetooth?] KASAN: slab-use-after-free Write in hci_conn_drop (3) syzbot
2026-02-09  7:50     ` #syz test kawada
2026-02-09  9:05       ` [syzbot] [bluetooth?] KASAN: slab-use-after-free Write in hci_conn_drop (3) syzbot
2026-02-08 20:31 ` syzbot [this message]
2025-12-03 11:28 syzbot
2025-12-04  1:03 ` Edward Adam Davis
2025-12-04  1:51   ` 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=6988f287.050a0220.3b3015.005f.GAE@google.com \
    --to=syzbot+3609b9b48e68e1fe47fd@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=youjingxiaogao2@gmail.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