From: syzbot <syzbot+062317ea1d0a6d5e29e7@syzkaller.appspotmail.com>
To: axboe@kernel.dk, brauner@kernel.org, chao@kernel.org,
daniel.vetter@ffwll.ch, hdanton@sina.com, jack@suse.cz,
jaegeuk@kernel.org, jinpu.wang@ionos.com,
linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
mairacanal@riseup.net, mcanal@igalia.com,
reiserfs-devel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
terrelln@fb.com, willy@infradead.org, yukuai3@huawei.com
Subject: Re: [f2fs-dev] [syzbot] [reiserfs?] possible deadlock in super_lock
Date: Sun, 08 Oct 2023 19:05:32 -0700 [thread overview]
Message-ID: <00000000000071133306073f06ca@google.com> (raw)
In-Reply-To: <0000000000001825ce06047bf2a6@google.com>
syzbot has bisected this issue to:
commit 7908632f2927b65f7486ae6b67c24071666ba43f
Author: Maíra Canal <mcanal@igalia.com>
Date: Thu Sep 14 10:19:02 2023 +0000
Revert "drm/vkms: Fix race-condition between the hrtimer and the atomic commit"
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17fc0565680000
start commit: 2cf0f7156238 Merge tag 'nfs-for-6.6-2' of git://git.linux-..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=14020565680000
console output: https://syzkaller.appspot.com/x/log.txt?x=10020565680000
kernel config: https://syzkaller.appspot.com/x/.config?x=710dc49bece494df
dashboard link: https://syzkaller.appspot.com/bug?extid=062317ea1d0a6d5e29e7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=107e9518680000
Reported-by: syzbot+062317ea1d0a6d5e29e7@syzkaller.appspotmail.com
Fixes: 7908632f2927 ("Revert "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+062317ea1d0a6d5e29e7@syzkaller.appspotmail.com>
To: axboe@kernel.dk, brauner@kernel.org, chao@kernel.org,
daniel.vetter@ffwll.ch, hdanton@sina.com, jack@suse.cz,
jaegeuk@kernel.org, jinpu.wang@ionos.com,
linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
mairacanal@riseup.net, mcanal@igalia.com,
reiserfs-devel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
terrelln@fb.com, willy@infradead.org, yukuai3@huawei.com
Subject: Re: [syzbot] [reiserfs?] possible deadlock in super_lock
Date: Sun, 08 Oct 2023 19:05:32 -0700 [thread overview]
Message-ID: <00000000000071133306073f06ca@google.com> (raw)
In-Reply-To: <0000000000001825ce06047bf2a6@google.com>
syzbot has bisected this issue to:
commit 7908632f2927b65f7486ae6b67c24071666ba43f
Author: Maíra Canal <mcanal@igalia.com>
Date: Thu Sep 14 10:19:02 2023 +0000
Revert "drm/vkms: Fix race-condition between the hrtimer and the atomic commit"
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17fc0565680000
start commit: 2cf0f7156238 Merge tag 'nfs-for-6.6-2' of git://git.linux-..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=14020565680000
console output: https://syzkaller.appspot.com/x/log.txt?x=10020565680000
kernel config: https://syzkaller.appspot.com/x/.config?x=710dc49bece494df
dashboard link: https://syzkaller.appspot.com/bug?extid=062317ea1d0a6d5e29e7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=107e9518680000
Reported-by: syzbot+062317ea1d0a6d5e29e7@syzkaller.appspotmail.com
Fixes: 7908632f2927 ("Revert "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-09 2:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-03 22:30 [f2fs-dev] [syzbot] [f2fs?] possible deadlock in super_lock syzbot
2023-09-03 22:30 ` syzbot
2023-09-20 9:13 ` [f2fs-dev] [syzbot] [reiserfs?] " syzbot
2023-09-20 9:13 ` syzbot
2023-10-08 15:14 ` [f2fs-dev] " syzbot
2023-10-08 15:14 ` syzbot
2023-10-09 2:05 ` syzbot [this message]
2023-10-09 2:05 ` syzbot
2023-10-09 12:37 ` [f2fs-dev] " Christian Brauner
2023-10-09 12:37 ` Christian Brauner
2023-10-09 14:19 ` [f2fs-dev] " syzbot
2023-10-09 14:19 ` syzbot
2023-12-24 16:40 ` [f2fs-dev] " syzbot
2023-12-24 16:40 ` syzbot
2023-12-28 10:50 ` [f2fs-dev] " Christian Brauner
2023-12-28 10:50 ` Christian Brauner
2024-01-02 12:14 ` [f2fs-dev] " Jan Kara
2024-01-02 12:14 ` Jan Kara
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=00000000000071133306073f06ca@google.com \
--to=syzbot+062317ea1d0a6d5e29e7@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=chao@kernel.org \
--cc=daniel.vetter@ffwll.ch \
--cc=hdanton@sina.com \
--cc=jack@suse.cz \
--cc=jaegeuk@kernel.org \
--cc=jinpu.wang@ionos.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mairacanal@riseup.net \
--cc=mcanal@igalia.com \
--cc=reiserfs-devel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=terrelln@fb.com \
--cc=willy@infradead.org \
--cc=yukuai3@huawei.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.