[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <00000000000017dd680608991d75@google.com>
Date: Wed, 25 Oct 2023 23:59:31 -0700
From: syzbot <syzbot+a4976ce949df66b1ddf1@...kaller.appspotmail.com>
To: arthurgrillo@...eup.net, chao@...nel.org, hdanton@...a.com,
jaegeuk@...nel.org, linux-f2fs-devel@...ts.sourceforge.net,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
lizhi.xu@...driver.com, mairacanal@...eup.net, mcanal@...lia.com,
penguin-kernel@...ove.sakura.ne.jp, syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [f2fs?] possible deadlock in f2fs_add_inline_entry
syzbot suspects this issue was fixed by commit:
commit a0e6a017ab56936c0405fe914a793b241ed25ee0
Author: MaĆra Canal <mcanal@...lia.com>
Date: Tue May 23 12:32:08 2023 +0000
drm/vkms: Fix race-condition between the hrtimer and the atomic commit
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=166c090d680000
start commit: 28f20a19294d Merge tag 'x86-urgent-2023-08-26' of git://gi..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=21a578092dd61d05
dashboard link: https://syzkaller.appspot.com/bug?extid=a4976ce949df66b1ddf1
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15a09340680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=118909eba80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: drm/vkms: Fix race-condition between the hrtimer and the atomic commit
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
Powered by blists - more mailing lists