From: Jason Gunthorpe <jgg@ziepe.ca>
To: syzbot <syzbot+48637757323884de77a2@syzkaller.appspotmail.com>
Cc: iommu@lists.linux.dev, joro@8bytes.org, kevin.tian@intel.com,
linux-kernel@vger.kernel.org, robin.murphy@arm.com,
syzkaller-bugs@googlegroups.com, will@kernel.org
Subject: Re: [syzbot] [iommu?] general protection fault in iommufd_ioas_change_process
Date: Tue, 18 Aug 2026 17:19:14 -0300 [thread overview]
Message-ID: <20260818201914.GA18100@ziepe.ca> (raw)
In-Reply-To: <6a833819.4d75e56a.c9a88.0001.GAE@google.com>
On Mon, Aug 17, 2026 at 09:34:33AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 3d6d817622b0 Merge tag 'scsi-fixes' of git://git.kernel.or..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=10b01a9e580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=c44651ea7dd2f307
> dashboard link: https://syzkaller.appspot.com/bug?extid=48637757323884de77a2
> compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13dbb225580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14b01a9e580000
#syz fix: iommu/iommufd: Fix NULL pointer deref in iommufd_ioas_change_process when racing with iopt_map_file_pages
next prev parent reply other threads:[~2026-08-18 20:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 16:34 [syzbot] [iommu?] general protection fault in iommufd_ioas_change_process syzbot
2026-08-18 1:53 ` Forwarded: [PATCH] iommufd: Fix NULL deref of area->pages in ioas_change_process syzbot
2026-08-18 20:19 ` Jason Gunthorpe [this message]
[not found] <20260818015323.19948-1-kartikey406@gmail.com>
2026-08-18 2:17 ` [syzbot] [iommu?] general protection fault in iommufd_ioas_change_process syzbot
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=20260818201914.GA18100@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=syzbot+48637757323884de77a2@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=will@kernel.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