All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+b170dbf55520ebf5969a@syzkaller.appspotmail.com>
To: abysamross@gmail.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] WARNING: ODEBUG bug in hci_release_dev (2)
Date: Tue, 17 Mar 2026 08:34:03 -0700	[thread overview]
Message-ID: <69b9746b.a00a0220.3b25d1.002f.GAE@google.com> (raw)
In-Reply-To: <20260317151156.463873-1-abysamross@gmail.com>

Hello,

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

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

Tested on:

commit:         2d1373e4 Merge tag 'for-7.0-rc4-tag' of git://git.kern..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1130e2d6580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=6f764aea3bbb63e1
dashboard link: https://syzkaller.appspot.com/bug?extid=b170dbf55520ebf5969a
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=17fea8da580000

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

       reply	other threads:[~2026-03-17 15:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260317151156.463873-1-abysamross@gmail.com>
2026-03-17 15:34 ` syzbot [this message]
     [not found] <20260321112739.139088-1-abysamross@gmail.com>
2026-03-21 11:50 ` [syzbot] [bluetooth?] WARNING: ODEBUG bug in hci_release_dev (2) syzbot
     [not found] <20260321104856.53049-1-abysamross@gmail.com>
2026-03-21 11:05 ` syzbot
     [not found] <20260316160751.297206-1-abysamross@gmail.com>
2026-03-16 16:24 ` syzbot
2024-07-24 13:25 syzbot
2024-10-14 23:11 ` syzbot
2024-12-21 14:19 ` 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=69b9746b.a00a0220.3b25d1.002f.GAE@google.com \
    --to=syzbot+b170dbf55520ebf5969a@syzkaller.appspotmail.com \
    --cc=abysamross@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.