syzbot has bisected this issue to:
commit 82ede9c19839079e7953a47895729852a440080c
Author: Wolfram Sang <[email protected]>
Date: Tue Jun 21 14:46:53 2022 +0000
scsi: ufs: core: Fix typos in error messages
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=132b298b480000
start commit: a689b938df39 Merge tag 'block-2023-01-06' of git://git.ker..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=10ab298b480000
console output: https://syzkaller.appspot.com/x/log.txt?x=172b298b480000
kernel config: https://syzkaller.appspot.com/x/.config?x=33ad6720950f996d
dashboard link: https://syzkaller.appspot.com/bug?extid=38e6635a03c83c76297a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=114dd83a480000
Reported-by: [email protected]
Fixes: 82ede9c19839 ("scsi: ufs: core: Fix typos in error messages")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
On 2/3/23 00:53, syzbot wrote:
> syzbot has bisected this issue to:
>
> commit 82ede9c19839079e7953a47895729852a440080c
> Author: Wolfram Sang <[email protected]>
> Date: Tue Jun 21 14:46:53 2022 +0000
>
> scsi: ufs: core: Fix typos in error messages
To the syzbot maintainers: I think this is a good example of a bisection
result that is wrong. It is unlikely that fixing typos in kernel
messages would affect whether or not the kernel hangs. Additionally, as
far as I know, the systems used by syzbot (Google Compute Engine virtual
machines) do trigger any code in the UFS driver.
Bart.