From: syzbot <syzbot+f52b6db1fe57bfb08d49@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] Re: [syzbot] [bluetooth?] WARNING in __hci_cmd_sync_sk
Date: Tue, 06 Aug 2024 07:28:15 -0700 [thread overview]
Message-ID: <000000000000ae8596061f049afc@google.com> (raw)
In-Reply-To: <000000000000fa6583061ccb8e3d@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: Re: [syzbot] [bluetooth?] WARNING in __hci_cmd_sync_sk
Author: djahchankoike@gmail.com
#syz fix: Bluetooth: L2CAP: Fix deadlock
Fixed upstream.
On Tue, Aug 6, 2024 at 10:45 AM syzbot <
syzbot+f52b6db1fe57bfb08d49@syzkaller.appspotmail.com> wrote:
> Hello,
>
> syzbot tried to test the proposed patch but the build/boot failed:
>
> failed to apply patch:
> checking file net/bluetooth/hci_core.c
> patch: **** unexpected end of file in patch
>
>
>
> Tested on:
>
> commit: b446a2da Merge tag 'linux_kselftest-fixes-6.11-rc3' of..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=3456bae478301dc8
> dashboard link:
> https://syzkaller.appspot.com/bug?extid=f52b6db1fe57bfb08d49
> compiler:
> patch:
> https://syzkaller.appspot.com/x/patch.diff?x=17b4c0f5980000
>
>
prev parent reply other threads:[~2024-08-06 14:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 7:34 [syzbot] [bluetooth?] WARNING in __hci_cmd_sync_sk syzbot
2024-07-10 13:49 ` syzbot
2024-08-06 3:26 ` [syzbot] " syzbot
2024-08-06 13:43 ` [syzbot] Re: [syzbot] [bluetooth?] " syzbot
2024-08-06 14:28 ` syzbot [this message]
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=000000000000ae8596061f049afc@google.com \
--to=syzbot+f52b6db1fe57bfb08d49@syzkaller.appspotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).