All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Baolu Lu <baolu.lu@linux.intel.com>
Cc: Pengfei Xu <pengfei.xu@intel.com>,
	iommu@lists.linux.dev, kevin.tian@intel.com, nicolinc@nvidia.com,
	heng.su@intel.com, rafael.j.wysocki@intel.com, lenb@kernel.org,
	lkp@intel.com
Subject: Re: [Syzkaller & bisect] There is general protection fault in iommu_device_unlink in upstream patch
Date: Wed, 2 Aug 2023 09:26:51 -0300	[thread overview]
Message-ID: <ZMpLi4TP9//n8EU3@nvidia.com> (raw)
In-Reply-To: <027e7c04-2d92-0b00-a504-56f51fc48520@linux.intel.com>

On Wed, Aug 02, 2023 at 03:53:03PM +0800, Baolu Lu wrote:

> This bug does not reproduce in the testing of hot adding and removing
> PCI devices on bare metal. Is it possible that this is related to the
> implementation of the mock device for iommufd selftest?

The reproducer works on my test VM, I intend to look into it today..

I guess it is because iommufd mock doesn't use the probe path, I might
have already fixed it when I redid this in the series to fix the
default domains.

Jason

  reply	other threads:[~2023-08-02 12:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01 13:46 [Syzkaller & bisect] There is general protection fault in iommu_device_unlink in upstream patch Pengfei Xu
2023-08-02  7:53 ` Baolu Lu
2023-08-02 12:26   ` Jason Gunthorpe [this message]
2023-08-03  0:21 ` Jason Gunthorpe
2023-08-03  1:04   ` Pengfei Xu

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=ZMpLi4TP9//n8EU3@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=heng.su@intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=kevin.tian@intel.com \
    --cc=lenb@kernel.org \
    --cc=lkp@intel.com \
    --cc=nicolinc@nvidia.com \
    --cc=pengfei.xu@intel.com \
    --cc=rafael.j.wysocki@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.