From: Krzysztof Mazur <krzysiek@podlesie.net>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-usb@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
Daniel J Blueman <daniel@numascale-asia.com>
Subject: Re: [PATCH 1/2] usb: fix cleanup after failure in hub_configure()
Date: Tue, 20 Aug 2013 20:42:36 +0200 [thread overview]
Message-ID: <20130820184236.GA782@shrek.podlesie.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1308201412220.1591-100000@iolanthe.rowland.org>
On Tue, Aug 20, 2013 at 02:14:42PM -0400, Alan Stern wrote:
> On Tue, 20 Aug 2013, Krzysztof Mazur wrote:
>
> > If the hub_configure() fails after setting the hdev->maxchild
> > the hub->ports might be NULL or point to uninitialized kzallocated
> > memory causing NULL pointer dereference in hub_quiesce() during cleanup.
> >
> > Now after such error the hdev->maxchild is set to 0 to avoid cleanup
> > of uninitialized ports.
>
> The idea is good, but the implementation is a little silly...
>
> > Suggested-by: Alan Stern <stern@rowland.harvard.edu>
> > Signed-off-by: Krzysztof Mazur <krzysiek@podlesie.net>
> > ---
> > drivers/usb/core/hub.c | 12 +++++++-----
> > 1 file changed, 7 insertions(+), 5 deletions(-)
> >
> > diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c
> > index 558313d..588c3a3 100644
> > --- a/drivers/usb/core/hub.c
> > +++ b/drivers/usb/core/hub.c
> > @@ -1339,7 +1339,7 @@ static int hub_configure(struct usb_hub *hub,
> > GFP_KERNEL);
> > if (!hub->ports) {
> > ret = -ENOMEM;
> > - goto fail;
> > + goto fail_maxchild;
> > }
> >
> > wHubCharacteristics = le16_to_cpu(hub->descriptor->wHubCharacteristics);
>
> > @@ -1567,6 +1567,8 @@ static int hub_configure(struct usb_hub *hub,
> > hub_activate(hub, HUB_INIT);
> > return 0;
> >
> > +fail_maxchild:
> > + hdev->maxchild = 0;
> > fail:
> > dev_err (hub_dev, "config failed, %s (err %d)\n",
> > message, ret);
>
> Why bother with a separate jump label? Just set maxchild to 0 whenever
> a failure occurs.
>
Initially I had just straightforward "dev->maxchild = 0;" after fail,
but I changed that to simplify the second patch and be able to
use goto fail:
ret = usb_hub_create_port_device(hub, i + 1);
if (ret < 0) {
dev_err(hub->intfdev,
"couldn't create port%d device.\n", i + 1);
hdev->maxchild = i;
goto fail;
}
and avoid "return ret" here or something like
if (hdev->maxchild == hub->descriptor->bNbrPorts)
hdev->maxchild = 0;
in the fail path.
Thanks,
Krzysiek
-- >8 --
Subject: [PATCH 1/2 v2] usb: fix cleanup after failure in hub_configure()
If the hub_configure() fails after setting the hdev->maxchild
the hub->ports might be NULL or point to uninitialized kzallocated
memory causing NULL pointer dereference in hub_quiesce() during cleanup.
Now after such error the hdev->maxchild is set to 0 to avoid cleanup
of uninitialized ports.
Signed-off-by: Krzysztof Mazur <krzysiek@podlesie.net>
---
drivers/usb/core/hub.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c
index 558313d..affed11 100644
--- a/drivers/usb/core/hub.c
+++ b/drivers/usb/core/hub.c
@@ -1568,6 +1568,7 @@ static int hub_configure(struct usb_hub *hub,
return 0;
fail:
+ hdev->maxchild = 0;
dev_err (hub_dev, "config failed, %s (err %d)\n",
message, ret);
/* hub_disconnect() frees urb and descriptor */
--
1.8.4.rc1.409.gbd48715
next prev parent reply other threads:[~2013-08-20 18:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 17:24 [PATCH 0/2] usb: fix hub_configure() error handling Krzysztof Mazur
2013-08-20 17:24 ` [PATCH 1/2] usb: fix cleanup after failure in hub_configure() Krzysztof Mazur
2013-08-20 18:14 ` Alan Stern
2013-08-20 18:42 ` Krzysztof Mazur [this message]
2013-08-20 18:59 ` Alan Stern
2013-08-20 19:16 ` Krzysztof Mazur
2013-08-20 19:51 ` Alan Stern
2013-08-20 17:24 ` [PATCH 2/2] usb: fail on usb_hub_create_port_device() errors Krzysztof Mazur
2013-08-20 18:18 ` Alan Stern
2013-08-20 19:07 ` Krzysztof Mazur
2013-08-20 19:50 ` Alan Stern
2013-08-21 9:25 ` Krzysztof Mazur
2013-08-21 14:25 ` 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=20130820184236.GA782@shrek.podlesie.net \
--to=krzysiek@podlesie.net \
--cc=daniel@numascale-asia.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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®