From: David Brownell <david-b@pacbell.net>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Andrew Morton <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>,
Benedikt Spranger <bene@linutronix.de>,
Stable Team <stable@kernel.org>
Subject: Re: [PATCH] usb-gadget-ether: Prevent oops caused by error interrupt race
Date: Fri, 21 Sep 2007 15:08:42 -0700 [thread overview]
Message-ID: <200709211508.42968.david-b@pacbell.net> (raw)
In-Reply-To: <1190299611.3481.34.camel@chaos>
On Thursday 20 September 2007, Thomas Gleixner wrote:
> From: Benedikt Spranger <bene@linutronix.de>
>
> An USB error interrupt (e.g. disconnect) nukes the pending requests for
> an ethernet gadget device asynchronously. This can race against
> eth_start_xmit(), where we end up dereferencing the list head itself.
>
> The nuke code is serialized against eth_start_xmit via dev->req_lock,
> but we need to check the list for empty first instead of unconditionally
> accessing dev->tx_reqs.next.
Looks OK, although the comments are confusingly incorrect which
made it hard to see what this was doing:
- There is no "nuke()" method in this driver, even comments
don't use that term.
- When "nuke" is used in the gadget stack, it means the way
that controller drivers scrub out a queue of live requests
queued to an endpoint ... *NOT* recycling memory that sits
on a freelist, which is what's involved here.
- Disconnect is *NOT* an error, it's a routine occurrence
which can happen at essentially any time.
If you update the patch and comments accordingly, ACK.
> This is a long standing bug, which should be fixed in stable as well.
>
> Signed-off-by: Benedikt Spranger <bene@linutronix.de>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
>
> diff --git a/drivers/usb/gadget/ether.c b/drivers/usb/gadget/ether.c
> index 593e235..f1d7c82 100644
> --- a/drivers/usb/gadget/ether.c
> +++ b/drivers/usb/gadget/ether.c
> @@ -1989,8 +1989,20 @@ static int eth_start_xmit (struct sk_buff *skb, struct net_device *net)
> }
>
> spin_lock_irqsave(&dev->req_lock, flags);
> + /*
> + * dev->tx_reqs may be empty due to an error interrupt which
Please reword: "may be empty because disconnecting an
active device cleans out this freelist".
> + * nuked all requests.
> + */
> + if (list_empty(&dev->tx_reqs)) {
> + netif_stop_queue(net);
> + spin_unlock_irqrestore(&dev->req_lock, flags);
> + return 1;
> + }
> +
> req = container_of (dev->tx_reqs.next, struct usb_request, list);
> list_del (&req->list);
> +
> + /* last request in list: stop queue */
> if (list_empty (&dev->tx_reqs))
> netif_stop_queue (net);
> spin_unlock_irqrestore(&dev->req_lock, flags);
>
>
next prev parent reply other threads:[~2007-09-21 22:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-20 14:46 [PATCH] usb-gadget-ether: Prevent oops caused by error interrupt race Thomas Gleixner
2007-09-21 22:08 ` David Brownell [this message]
2007-09-22 17:41 ` [PATCH] usb-gadget-ether: Prevent oops caused by error interrupt race -V2 (comments update) Thomas Gleixner
2007-09-22 19:18 ` David Brownell
2007-09-22 19:30 ` Thomas Gleixner
2007-09-22 20:14 ` David Brownell
2007-09-22 20:23 ` Thomas Gleixner
2007-09-22 20:53 ` David Brownell
2007-09-22 23:32 ` Thomas Gleixner
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=200709211508.42968.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=akpm@osdl.org \
--cc=bene@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=tglx@linutronix.de \
/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