From: syzbot <syzbot+51baee846ddab52d5230@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, davem@davemloft.net,
dvyukov@google.com, edumazet@google.com,
johan.hedberg@gmail.com, kuba@kernel.org,
linux-bluetooth@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, luiz.dentz@gmail.com,
luiz.von.dentz@intel.com, marcel@holtmann.org,
netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com, torvalds@linux-foundation.org,
william.xuanziyang@huawei.com, willy@infradead.org,
wzhmmmmm@gmail.com
Subject: Re: [syzbot] [bluetooth?] KASAN: null-ptr-deref Read in ida_free (4)
Date: Sun, 11 Feb 2024 01:55:05 -0800 [thread overview]
Message-ID: <000000000000d4a29506111827e7@google.com> (raw)
In-Reply-To: <000000000000a135c0060a2260b3@google.com>
syzbot suspects this issue was fixed by commit:
commit af73483f4e8b6f5c68c9aa63257bdd929a9c194a
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date: Thu Dec 21 16:53:57 2023 +0000
ida: Fix crash in ida_free when the bitmap is empty
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12fc6ba2180000
start commit: b46ae77f6787 Merge tag 'xfs-6.7-fixes-3' of git://git.kern..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=6ae1a4ee971a7305
dashboard link: https://syzkaller.appspot.com/bug?extid=51baee846ddab52d5230
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=127837cce80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12779dc8e80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: ida: Fix crash in ida_free when the bitmap is empty
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-02-11 9:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000a135c0060a2260b3@google.com>
2023-11-26 11:15 ` [syzbot] [bluetooth?] KASAN: null-ptr-deref Read in ida_free (4) syzbot
2024-02-11 9:55 ` syzbot [this message]
2024-02-12 10:32 ` Aleksandr Nogikh
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=000000000000d4a29506111827e7@google.com \
--to=syzbot+51baee846ddab52d5230@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=william.xuanziyang@huawei.com \
--cc=willy@infradead.org \
--cc=wzhmmmmm@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;
as well as URLs for NNTP newsgroup(s).