From: syzbot <syzbot+7574ebfe589049630608@syzkaller.appspotmail.com>
To: alex.williamson@redhat.com, iommu@lists.linux.dev,
jgg@nvidia.com, jgg@ziepe.ca, joro@8bytes.org,
kevin.tian@intel.com, linux-kernel@vger.kernel.org,
nicolinc@nvidia.com, robin.murphy@arm.com,
syzkaller-bugs@googlegroups.com, terrence.xu@intel.com,
will@kernel.org, yi.l.liu@intel.com
Subject: Re: [syzbot] [iommu?] WARNING in iommufd_access_destroy
Date: Sat, 15 Jul 2023 19:57:23 -0700 [thread overview]
Message-ID: <0000000000005f80ad060091d7cb@google.com> (raw)
In-Reply-To: <00000000000054bd5b06006df9c8@google.com>
syzbot has bisected this issue to:
commit 54b47585db6658a5eb898d4d45be18d1e581c1bf
Author: Nicolin Chen <nicolinc@nvidia.com>
Date: Mon Mar 27 09:33:47 2023 +0000
iommufd: Create access in vfio_iommufd_emulated_bind()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16549b42a80000
start commit: b6e6cc1f78c7 Merge tag 'x86_urgent_for_6.5_rc2' of git://g..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=15549b42a80000
console output: https://syzkaller.appspot.com/x/log.txt?x=11549b42a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=6769a69bd0e144b4
dashboard link: https://syzkaller.appspot.com/bug?extid=7574ebfe589049630608
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=123562dca80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15825e1aa80000
Reported-by: syzbot+7574ebfe589049630608@syzkaller.appspotmail.com
Fixes: 54b47585db66 ("iommufd: Create access in vfio_iommufd_emulated_bind()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-07-16 2:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 8:09 [syzbot] [iommu?] WARNING in iommufd_access_destroy syzbot
2023-07-16 2:57 ` 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=0000000000005f80ad060091d7cb@google.com \
--to=syzbot+7574ebfe589049630608@syzkaller.appspotmail.com \
--cc=alex.williamson@redhat.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolinc@nvidia.com \
--cc=robin.murphy@arm.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=terrence.xu@intel.com \
--cc=will@kernel.org \
--cc=yi.l.liu@intel.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.