From: syzbot <syzbot+e70e4c6f6eee43357ba7@syzkaller.appspotmail.com>
To: akinobu.mita@gmail.com, akpm@linux-foundation.org,
alinde@google.com, dakr@redhat.com, glider@google.com,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, mcgrof@kernel.org, rafael@kernel.org,
russ.weight@linux.dev, syzkaller-bugs@googlegroups.com,
torvalds@linux-foundation.org
Subject: Re: [syzbot] [usb?] possible deadlock in assign_fw
Date: Fri, 30 Aug 2024 08:53:01 -0700 [thread overview]
Message-ID: <00000000000005da6a0620e8961e@google.com> (raw)
In-Reply-To: <00000000000040b643061ca951fe@google.com>
syzbot has bisected this issue to:
commit 4d0e9df5e43dba52d38b251e3b909df8fa1110be
Author: Albert van der Linde <alinde@google.com>
Date: Fri Oct 16 03:13:50 2020 +0000
lib, uaccess: add failure injection to usercopy functions
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=132abd2b980000
start commit: d5d547aa7b51 Merge tag 'random-6.11-rc6-for-linus' of git:..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=10aabd2b980000
console output: https://syzkaller.appspot.com/x/log.txt?x=172abd2b980000
kernel config: https://syzkaller.appspot.com/x/.config?x=d76559f775f44ba6
dashboard link: https://syzkaller.appspot.com/bug?extid=e70e4c6f6eee43357ba7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14ee2b7b980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=177c7b7b980000
Reported-by: syzbot+e70e4c6f6eee43357ba7@syzkaller.appspotmail.com
Fixes: 4d0e9df5e43d ("lib, uaccess: add failure injection to usercopy functions")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-08-30 15:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00000000000040b643061ca951fe@google.com>
2024-08-30 3:43 ` [syzbot] [usb?] possible deadlock in assign_fw syzbot
2024-08-30 15:53 ` 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=00000000000005da6a0620e8961e@google.com \
--to=syzbot+e70e4c6f6eee43357ba7@syzkaller.appspotmail.com \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alinde@google.com \
--cc=dakr@redhat.com \
--cc=glider@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=rafael@kernel.org \
--cc=russ.weight@linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.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 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).