linux-kernel - Re: [PATCH] bus: fsl-mc: don't assume child devices are all fsl-mc devices

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Y9kB8F3Nls8d1Koi@kroah.com>
Date:   Tue, 31 Jan 2023 12:56:32 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     laurentiu.tudor@....com
Cc:     linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        ioana.ciornei@....com
Subject: Re: [PATCH] bus: fsl-mc: don't assume child devices are all fsl-mc
 devices

On Fri, Jan 27, 2023 at 03:16:36PM +0200, laurentiu.tudor@....com wrote:
> From: Laurentiu Tudor <laurentiu.tudor@....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?

And what type of "pseudo device" is being created?  Why would it be
passed to this driver if it's the wrong type?

this feels wrong...

thanks,

greg k-h