From: syzbot <syzbot+9a44753ac327c557796a@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, chris@chris-wilson.co.uk,
dvyukov@google.com, jack@suse.cz, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, mika.kuoppala@linux.intel.com,
rodrigo.vivi@intel.com, syzkaller-bugs@googlegroups.com,
tytso@mit.edu
Subject: Re: WARNING in ext4_set_page_dirty
Date: Wed, 21 Oct 2020 15:45:06 -0700 [thread overview]
Message-ID: <0000000000005a390a05b2361916@google.com> (raw)
In-Reply-To: <089e0825cec8180a2b0568c4ee1d@google.com>
syzbot suspects this issue was fixed by commit:
commit 7dfbf8a07cf8c936b0d6cc810df6ae7923954d5b
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date: Tue Jun 30 15:27:24 2020 +0000
drm/i915: Skip stale object handle for debugfs per-file-stats
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=153d895f900000
start commit: 46cf053e Linux 5.5-rc3
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=ed9d672709340e35
dashboard link: https://syzkaller.appspot.com/bug?extid=9a44753ac327c557796a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10055799e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15b852c6e00000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: drm/i915: Skip stale object handle for debugfs per-file-stats
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-10-21 22:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-01 8:05 WARNING in ext4_set_page_dirty syzbot
2018-04-19 16:08 ` Jan Kara
2018-05-21 6:07 ` syzbot
2018-05-21 12:50 ` Jan Kara
2018-06-13 15:55 ` Dmitry Vyukov
2020-10-21 22:45 ` syzbot [this message]
2023-04-30 4:55 ` Theodore Ts'o
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=0000000000005a390a05b2361916@google.com \
--to=syzbot+9a44753ac327c557796a@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=chris@chris-wilson.co.uk \
--cc=dvyukov@google.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.kuoppala@linux.intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
/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).