From: syzbot <syzbot+8d1d62bfb63d6a480be1@syzkaller.appspotmail.com>
To: agruenba@redhat.com, akpm@linux-foundation.org,
arthurgrillo@riseup.net, cluster-devel@redhat.com,
gfs2@lists.linux.dev, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
mairacanal@riseup.net, mcanal@igalia.com, rpeterso@redhat.com,
syzkaller-bugs@googlegroups.com, willy@infradead.org
Subject: Re: [syzbot] [gfs2?] WARNING in folio_account_dirtied
Date: Thu, 01 Feb 2024 21:55:04 -0800 [thread overview]
Message-ID: <000000000000e7440306105fc0e2@google.com> (raw)
In-Reply-To: <000000000000f121b705df9f5a0a@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=11c75660180000
start commit: 1f5abbd77e2c Merge tag 'thermal-6.2-rc3' of git://git.kern..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=9babfdc3dd4772d0
dashboard link: https://syzkaller.appspot.com/bug?extid=8d1d62bfb63d6a480be1
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=139473cc480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17581426480000
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
prev parent reply other threads:[~2024-02-02 5:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000f121b705df9f5a0a@google.com>
2022-09-28 11:35 ` [syzbot] WARNING in folio_account_dirtied syzbot
2024-02-02 5:55 ` syzbot [this message]
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=000000000000e7440306105fc0e2@google.com \
--to=syzbot+8d1d62bfb63d6a480be1@syzkaller.appspotmail.com \
--cc=agruenba@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=arthurgrillo@riseup.net \
--cc=cluster-devel@redhat.com \
--cc=gfs2@lists.linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mairacanal@riseup.net \
--cc=mcanal@igalia.com \
--cc=rpeterso@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willy@infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).