From: syzbot <syzbot+79c403850e6816dc39cf@syzkaller.appspotmail.com>
To: alex.aring@gmail.com, amir73il@gmail.com, bfields@fieldses.org,
brauner@kernel.org, changlianzhi@uniontech.com,
chuck.lever@oracle.com, dmitry.torokhov@gmail.com,
gregkh@linuxfoundation.org, jack@suse.cz, jlayton@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [fs?] possible deadlock in input_inject_event
Date: Sat, 14 Dec 2024 18:25:03 -0800 [thread overview]
Message-ID: <675e3dff.050a0220.37aaf.00e5.GAE@google.com> (raw)
In-Reply-To: <66f6c8ce.050a0220.46d20.001c.GAE@google.com>
syzbot has bisected this issue to:
commit fb09d0ac07725b442b32dbf53f0ab0bea54804e9
Author: lianzhi chang <changlianzhi@uniontech.com>
Date: Wed Dec 15 12:51:25 2021 +0000
tty: Fix the keyboard led light display problem
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12ad3cdf980000
start commit: 7eef7e306d3c Merge tag 'for-6.13/dm-changes' of git://git...
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=11ad3cdf980000
console output: https://syzkaller.appspot.com/x/log.txt?x=16ad3cdf980000
kernel config: https://syzkaller.appspot.com/x/.config?x=8df9bf3383f5970
dashboard link: https://syzkaller.appspot.com/bug?extid=79c403850e6816dc39cf
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13bfd530580000
Reported-by: syzbot+79c403850e6816dc39cf@syzkaller.appspotmail.com
Fixes: fb09d0ac0772 ("tty: Fix the keyboard led light display problem")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-12-15 2:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-27 15:01 [syzbot] [fs?] possible deadlock in input_inject_event syzbot
2024-11-27 8:41 ` syzbot
2024-12-15 2:25 ` syzbot [this message]
2025-05-24 20:38 ` syzbot
[not found] <20250525010238.2312-1-hdanton@sina.com>
2025-05-25 1:24 ` 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=675e3dff.050a0220.37aaf.00e5.GAE@google.com \
--to=syzbot+79c403850e6816dc39cf@syzkaller.appspotmail.com \
--cc=alex.aring@gmail.com \
--cc=amir73il@gmail.com \
--cc=bfields@fieldses.org \
--cc=brauner@kernel.org \
--cc=changlianzhi@uniontech.com \
--cc=chuck.lever@oracle.com \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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