From: syzbot <syzbot+265e1cae90f8fa08f14d@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, davem@davemloft.net,
johan.hedberg@gmail.com, kuba@kernel.org, linma@zju.edu.cn,
linux-bluetooth@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
luiz.dentz@gmail.com, marcel@holtmann.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
willy@infradead.org
Subject: Re: [syzbot] [fs?] [mm?] INFO: task hung in page_cache_ra_unbounded (2)
Date: Mon, 02 Sep 2024 08:28:01 -0700 [thread overview]
Message-ID: <00000000000026b5250621249667@google.com> (raw)
In-Reply-To: <00000000000087bd88062117d676@google.com>
syzbot has bisected this issue to:
commit e305509e678b3a4af2b3cfd410f409f7cdaabb52
Author: Lin Ma <linma@zju.edu.cn>
Date: Sun May 30 13:37:43 2021 +0000
Bluetooth: use correct lock to prevent UAF of hdev object
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16a579eb980000
start commit: 431c1646e1f8 Linux 6.11-rc6
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=15a579eb980000
console output: https://syzkaller.appspot.com/x/log.txt?x=11a579eb980000
kernel config: https://syzkaller.appspot.com/x/.config?x=660f6eb11f9c7dc5
dashboard link: https://syzkaller.appspot.com/bug?extid=265e1cae90f8fa08f14d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16f8f0fb980000
Reported-by: syzbot+265e1cae90f8fa08f14d@syzkaller.appspotmail.com
Fixes: e305509e678b ("Bluetooth: use correct lock to prevent UAF of hdev object")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-09-02 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 0:15 [syzbot] [fs?] [mm?] INFO: task hung in page_cache_ra_unbounded (2) syzbot
2024-09-02 6:24 ` syzbot
2024-09-02 15: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=00000000000026b5250621249667@google.com \
--to=syzbot+265e1cae90f8fa08f14d@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linma@zju.edu.cn \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willy@infradead.org \
/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.