[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YhiZDy+y1/YmlWL2@kroah.com>
Date: Fri, 25 Feb 2022 09:53:35 +0100
From: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
To: "stern@...land.harvard.edu" <stern@...land.harvard.edu>
Cc: "Zhang, Qiang1" <qiang1.zhang@...el.com>,
Tejun Heo <tj@...nel.org>,
syzbot <syzbot+348b571beb5eeb70a582@...kaller.appspotmail.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"syzkaller-bugs@...glegroups.com" <syzkaller-bugs@...glegroups.com>,
"balbi@...nel.org" <balbi@...nel.org>
Subject: Re: [syzbot] KASAN: use-after-free Read in dev_uevent
On Thu, Feb 24, 2022 at 09:06:13PM -0500, stern@...land.harvard.edu wrote:
> On Thu, Feb 24, 2022 at 11:37:39PM +0100, gregkh@...uxfoundation.org wrote:
> > On Thu, Feb 24, 2022 at 04:23:26PM -0500, stern@...land.harvard.edu wrote:
> > > Can you tell us how this should be fixed?
> >
> > It should be fixed by properly using the driver core to bind/unbind the
> > driver to devices like I mentioned previously :)
>
> This would involve creating a "gadget" bus_type (or should it be a
> device_type under the platform bus?) and registering the gadgets
> on it, right?.
Yes. Or you can use the aux bus for this, which might be easier.
> Similarly, the gadget drivers would be registered on
> this bus. I suppose we can control which drivers get bound to which
> gadgets with careful matching code.
The aux bus might make this easier:
Documentation/driver-api/auxiliary_bus.rst
thanks,
greg k-h
Powered by blists - more mailing lists