From: Laurentiu Tudor <laurentiu.tudor@nxp.com>
To: Greg KH <gregkh@linuxfoundation.org>
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 13:50:11 +0200 [thread overview]
Message-ID: <d6297aae-7f9e-1b4e-d2f3-da5664804ab0@nxp.com> (raw)
In-Reply-To: <Y9kB8F3Nls8d1Koi@kroah.com>
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.
> 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.
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3c28a76124b25882411f005924be73795b6ef078
[2]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/bus/fsl-mc/dprc-driver.c?#n96
---
Thanks & Best Regards, Laurentiu
next prev parent reply other threads:[~2023-02-01 11:50 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 [this message]
2023-02-01 13:04 ` Greg KH
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=d6297aae-7f9e-1b4e-d2f3-da5664804ab0@nxp.com \
--to=laurentiu.tudor@nxp.com \
--cc=gregkh@linuxfoundation.org \
--cc=ioana.ciornei@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®