From: syzbot <syzbot+a4976ce949df66b1ddf1@syzkaller.appspotmail.com>
To: arthurgrillo@riseup.net, chao@kernel.org, hdanton@sina.com,
jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
lizhi.xu@windriver.com, mairacanal@riseup.net,
mcanal@igalia.com, penguin-kernel@i-love.sakura.ne.jp,
syzkaller-bugs@googlegroups.com
Subject: Re: [f2fs-dev] [syzbot] [f2fs?] possible deadlock in f2fs_add_inline_entry
Date: Wed, 25 Oct 2023 23:59:31 -0700 [thread overview]
Message-ID: <00000000000017dd680608991d75@google.com> (raw)
In-Reply-To: <0000000000000f188605ffdd9cf8@google.com>
syzbot suspects this issue was fixed by commit:
commit a0e6a017ab56936c0405fe914a793b241ed25ee0
Author: Maíra Canal <mcanal@igalia.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
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+a4976ce949df66b1ddf1@syzkaller.appspotmail.com>
To: arthurgrillo@riseup.net, chao@kernel.org, hdanton@sina.com,
jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
lizhi.xu@windriver.com, mairacanal@riseup.net,
mcanal@igalia.com, penguin-kernel@i-love.sakura.ne.jp,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [f2fs?] possible deadlock in f2fs_add_inline_entry
Date: Wed, 25 Oct 2023 23:59:31 -0700 [thread overview]
Message-ID: <00000000000017dd680608991d75@google.com> (raw)
In-Reply-To: <0000000000000f188605ffdd9cf8@google.com>
syzbot suspects this issue was fixed by commit:
commit a0e6a017ab56936c0405fe914a793b241ed25ee0
Author: Maíra Canal <mcanal@igalia.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
next prev parent reply other threads:[~2023-10-26 6:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 3:55 [f2fs-dev] [syzbot] [f2fs?] possible deadlock in f2fs_add_inline_entry syzbot
2023-07-07 3:55 ` syzbot
2023-08-24 15:55 ` [f2fs-dev] " syzbot
2023-08-24 15:55 ` syzbot
2023-08-25 1:08 ` [f2fs-dev] " Chao Yu
2023-08-25 1:08 ` Chao Yu
2023-08-25 1:47 ` [f2fs-dev] " syzbot
2023-08-25 1:47 ` syzbot
2023-08-25 5:37 ` [f2fs-dev] [PATCH] f2fs: fix deadlock in f2f2_add_dentry Lizhi Xu via Linux-f2fs-devel
2023-08-25 5:37 ` Lizhi Xu
2023-08-25 10:41 ` [f2fs-dev] " Chao Yu
2023-08-25 10:41 ` Chao Yu
2023-08-26 2:58 ` [f2fs-dev] " Lizhi Xu via Linux-f2fs-devel
2023-08-26 2:58 ` Lizhi Xu
2023-09-06 12:56 ` Tetsuo Handa
2023-09-06 12:56 ` Tetsuo Handa
2023-10-26 6:59 ` syzbot [this message]
2023-10-26 6:59 ` [syzbot] [f2fs?] possible deadlock in f2fs_add_inline_entry syzbot
2023-10-26 9:21 ` [f2fs-dev] " Aleksandr Nogikh via Linux-f2fs-devel
2023-10-26 9:21 ` Aleksandr Nogikh
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=00000000000017dd680608991d75@google.com \
--to=syzbot+a4976ce949df66b1ddf1@syzkaller.appspotmail.com \
--cc=arthurgrillo@riseup.net \
--cc=chao@kernel.org \
--cc=hdanton@sina.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.xu@windriver.com \
--cc=mairacanal@riseup.net \
--cc=mcanal@igalia.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=syzkaller-bugs@googlegroups.com \
/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.