From: syzbot <syzbot+abe01a74653f00aabe3e@syzkaller.appspotmail.com>
To: airlied@linux.ie, daniel@ffwll.ch,
dri-devel@lists.freedesktop.org,
linux-graphics-maintainer@vmware.com,
linux-kernel@vger.kernel.org, reiserfs-devel@vger.kernel.org,
sroland@vmware.com, syzkaller-bugs@googlegroups.com,
tzimmermann@suse.de, zackr@vmware.com
Subject: Re: [syzbot] possible deadlock in vfs_fileattr_set
Date: Sun, 13 Nov 2022 17:49:38 -0800 [thread overview]
Message-ID: <000000000000c7f9c605ed6473c8@google.com> (raw)
In-Reply-To: <00000000000041665a05ed5c17db@google.com>
syzbot has bisected this issue to:
commit 6dd6b7643e723b4779e59c8ad97bd5db6ff3bb12
Author: Thomas Zimmermann <tzimmermann@suse.de>
Date: Mon Jan 18 13:14:19 2021 +0000
drm/vmwgfx: Remove reference to struct drm_device.pdev
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1418e6a5880000
start commit: f8f60f322f06 Add linux-next specific files for 20221111
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=1618e6a5880000
console output: https://syzkaller.appspot.com/x/log.txt?x=1218e6a5880000
kernel config: https://syzkaller.appspot.com/x/.config?x=85ba52c07cd97289
dashboard link: https://syzkaller.appspot.com/bug?extid=abe01a74653f00aabe3e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=138b76ae880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16ab1bfe880000
Reported-by: syzbot+abe01a74653f00aabe3e@syzkaller.appspotmail.com
Fixes: 6dd6b7643e72 ("drm/vmwgfx: Remove reference to struct drm_device.pdev")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2022-11-14 1:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-13 15:51 [syzbot] possible deadlock in vfs_fileattr_set syzbot
2022-11-14 1:49 ` 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=000000000000c7f9c605ed6473c8@google.com \
--to=syzbot+abe01a74653f00aabe3e@syzkaller.appspotmail.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-graphics-maintainer@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=sroland@vmware.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tzimmermann@suse.de \
--cc=zackr@vmware.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).