From: Michal Nazarewicz <mina86@mina86.com>
To: oskar.andero@sonymobile.com, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Felipe Balbi <balbi@ti.com>,
Radovan.Lekanovic@sonymobile.com,
Truls Bengtsson <truls.bengtsson@sonymobile.com>,
Oskar Andero <oskar.andero@sonymobile.com>
Subject: Re: [RFC PATCHv2 1/1] usb: f_rndis: Avoid to use ERROR macro if cdev can be null
Date: Tue, 19 Mar 2013 14:22:56 +0100 [thread overview]
Message-ID: <xa1t7gl3a5hr.fsf@mina86.com> (raw)
In-Reply-To: <1363691503-15581-2-git-send-email-oskar.andero@sonymobile.com>
[-- Attachment #1: Type: text/plain, Size: 2149 bytes --]
On Tue, Mar 19 2013, oskar.andero@sonymobile.com wrote:
> The udc_irq service runs the isr_tr_complete_handler which in turn
> "nukes" the endpoints, including a call to rndis_response_complete,
> if appropriate. If the rndis_msg_parser fails here, an error will
> be printed using a dev_err call (through the ERROR() macro).
>
> However, if the usb cable was just disconnected the device (cdev)
> might not be available and will be null. Since the dev_err macro will
> dereference the cdev pointer we get a null pointer exception.
>
> Reviewed-by: Radovan Lekanovic <radovan.lekanovic@sonymobile.com>
> Signed-off-by: Truls Bengtsson <truls.bengtsson@sonymobile.com>
> Signed-off-by: Oskar Andero <oskar.andero@sonymobile.com>
Acked-by: Michal Nazarewicz <mina86@mina86.com>
I think this is the best solution. Adding if statements around it would
just add noise.
> ---
> drivers/usb/gadget/f_rndis.c | 3 +--
> 1 files changed, 1 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/usb/gadget/f_rndis.c b/drivers/usb/gadget/f_rndis.c
> index 71beeb8..cc9c49c 100644
> --- a/drivers/usb/gadget/f_rndis.c
> +++ b/drivers/usb/gadget/f_rndis.c
> @@ -447,14 +447,13 @@ static void rndis_response_complete(struct usb_ep *ep, struct usb_request *req)
> static void rndis_command_complete(struct usb_ep *ep, struct usb_request *req)
> {
> struct f_rndis *rndis = req->context;
> - struct usb_composite_dev *cdev = rndis->port.func.config->cdev;
> int status;
>
> /* received RNDIS command from USB_CDC_SEND_ENCAPSULATED_COMMAND */
> // spin_lock(&dev->lock);
> status = rndis_msg_parser(rndis->config, (u8 *) req->buf);
> if (status < 0)
> - ERROR(cdev, "RNDIS command error %d, %d/%d\n",
> + pr_err("RNDIS command error %d, %d/%d\n",
> status, req->actual, req->length);
> // spin_unlock(&dev->lock);
> }
--
Best regards, _ _
.o. | Liege of Serenely Enlightened Majesty of o' \,=./ `o
..o | Computer Science, Michał “mina86” Nazarewicz (o o)
ooo +----<email/xmpp: mpn@google.com>--------------ooO--(_)--Ooo--
[-- Attachment #2.1: Type: text/plain, Size: 0 bytes --]
[-- Attachment #2.2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2013-03-19 13:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 11:11 [RFC PATCHv2 0/1] usb: f_rndis: Avoid to use ERROR macro if cdev can be null oskar.andero
2013-03-19 11:11 ` [RFC PATCHv2 1/1] " oskar.andero
2013-03-19 13:22 ` Michal Nazarewicz [this message]
2013-03-20 12:51 ` Felipe Balbi
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=xa1t7gl3a5hr.fsf@mina86.com \
--to=mina86@mina86.com \
--cc=Radovan.Lekanovic@sonymobile.com \
--cc=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oskar.andero@sonymobile.com \
--cc=truls.bengtsson@sonymobile.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