mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Laurentiu Tudor <laurentiu.tudor@nxp.com>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, ioana.ciornei@nxp.com
Subject: Re: [PATCH] bus: fsl-mc: don't assume child devices are all fsl-mc devices
Date: Wed, 1 Feb 2023 14:04:41 +0100	[thread overview]
Message-ID: <Y9pjaQVOda8tY/Qt@kroah.com> (raw)
In-Reply-To: <d6297aae-7f9e-1b4e-d2f3-da5664804ab0@nxp.com>

On Wed, Feb 01, 2023 at 01:50:11PM +0200, Laurentiu Tudor wrote:
> Hi Greg,
> 
> On 1/31/2023 1:56 PM, Greg KH wrote:
> > On Fri, Jan 27, 2023 at 03:16:36PM +0200, laurentiu.tudor@nxp.com wrote:
> > > From: Laurentiu Tudor <laurentiu.tudor@nxp.com>
> > > 
> > > Changes in VFIO caused a pseudo-device to be created as child of
> > > fsl-mc devices causing a crash [1] when trying to bind a fsl-mc
> > > device to VFIO. Fix this by checking the device type when enumerating
> > > fsl-mc child devices.
> > 
> > What changes?  What commit id does this fix?  Does it need to be
> > backported?
> 
> There were a lot of changes in the VFIO area but I'd point at this commit
> [1].
> 
> I'll resend the patch with a "Fixes:" tag pointing at this commit if that's
> ok with you.

Please do.

> > And what type of "pseudo device" is being created? Why would it be
> > passed to this driver if it's the wrong type?
> 
> It's not passed to the driver per-se. The problem shows up when the
> implementation of the driver does a device_for_each_child() [2] and the
> callback blindly assumes that all enumerated children devices are fsl-mc
> devices. The patch just adds a check for this case.

Ah, that makes more sense, sorry for the noise.

greg k-h

      reply	other threads:[~2023-02-01 13:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-27 13:16 laurentiu.tudor
2023-01-31 11:56 ` Greg KH
2023-02-01 11:50   ` Laurentiu Tudor
2023-02-01 13:04     ` Greg KH [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=Y9pjaQVOda8tY/Qt@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ioana.ciornei@nxp.com \
    --cc=laurentiu.tudor@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®