From: Greg KH <greg@kroah.com>
To: poma <pomidorabelisima@gmail.com>
Cc: Jes Sorensen <Jes.Sorensen@redhat.com>,
Xose Vazquez Perez <xose.vazquez@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: rtl8xxxu 4.4.5(from f23): I get a panic adding a new device to the driver
Date: Thu, 17 Mar 2016 13:42:48 -0700 [thread overview]
Message-ID: <20160317204248.GA12102@kroah.com> (raw)
In-Reply-To: <56EB0D15.9040103@gmail.com>
On Thu, Mar 17, 2016 at 09:01:25PM +0100, poma wrote:
> On 17.03.2016 19:02, Jes Sorensen wrote:
> > Jes Sorensen <Jes.Sorensen@redhat.com> writes:
> >> Xose Vazquez Perez <xose.vazquez@gmail.com> writes:
> >>> Hi,
> >>>
> >>> If I do:
> >>> # echo "0bda 8176" > /sys/bus/usb/drivers/rtl8xxxu/new_id
> >>
> >> Hi Xose,
> >>
> >> Yes please don't do that. The rtl8xxxu driver relies on the .driver_info
> >> field in struct use_device_id to carry information for the different
> >> types of devices. If you hot add a device like above, the driver will
> >> fail because that field now contains a NULL pointer.
> >>
> >> I should probably add a check for it in the probe function, but it will
> >> simply be there to spit out a warning that it doesn't work to hot add a
> >> device like this.
> >>
> >> If you build it with CONFIG_RTL8XXXU_UNTESTED the 0bda:8176 should be
> >> included in the device list.
> >>
> >> Cheers,
> >> Jes
> >
> > Hi Xose,
> >
> > I added the following patch to my tree to avoid this.
> >
> > Cheers,
> > Jes
> >
> > commit 9202f4947aac1d60084ee79c9b5294eb42ba59dc
> > Author: Jes Sorensen <Jes.Sorensen@redhat.com>
> > Date: Thu Mar 17 13:53:48 2016 -0400
> >
> > rtl8xxxu: Fix OOPS if user tries to add device via /sys
> >
> > This driver relies on driver_info in struct usb_device_id, hence
> > adding a device via /sys/bus/usb/drivers/rtl8xxxu/new_id would result
> > in a NULL pointer dereference.
> >
> > Instead print a message and return -ENODEV
> >
> > Reported-by: Xose Vazquez Perez <xose.vazquez@gmail.com>
> > Signed-off-by: Jes Sorensen <Jes.Sorensen@redhat.com>
> >
> > diff --git a/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.c b/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.c
> > index 8d893f4..55fc00e 100644
> > --- a/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.c
> > +++ b/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.c
> > @@ -9671,6 +9671,15 @@ static int rtl8xxxu_probe(struct usb_interface *interface,
> >
> > udev = usb_get_dev(interface_to_usbdev(interface));
> >
> > + if (!id->driver_info) {
> > + dev_warn(&udev->dev,
> > + "rtl8xxxu relies on driver_info in struct usb_device_id.\n");
> > + dev_warn(&udev->dev,
> > + "Adding a device via /sys/bus/usb/drivers/rtl8xxxu/new_id is not supported!\n");
We do have a flag in the USB driver structure to prevent this from
happening, "no_dynamic_id", please just set that and then this should
not happen.
thanks,
gre k-h
next prev parent reply other threads:[~2016-03-17 20:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 23:42 rtl8xxxu 4.4.5(from f23): I get a panic adding a new device to the driver Xose Vazquez Perez
2016-03-16 13:58 ` Jes Sorensen
2016-03-17 18:02 ` Jes Sorensen
2016-03-17 20:01 ` poma
2016-03-17 20:11 ` Jes Sorensen
2016-03-17 20:42 ` Greg KH [this message]
2016-03-17 21:47 ` Jes Sorensen
2016-03-17 20:50 ` Alan Stern
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=20160317204248.GA12102@kroah.com \
--to=greg@kroah.com \
--cc=Jes.Sorensen@redhat.com \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pomidorabelisima@gmail.com \
--cc=xose.vazquez@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).