From: Sergei Shtylyov <sshtylyov@mvista.com>
To: navin patidar <navinp@cdac.in>
Cc: gregkh@linuxfoundation.org, mfm@muteddisk.com,
linux-usb@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: usbip: stub_dev: Fixed oops during removal of usbip_host
Date: Fri, 14 Sep 2012 15:42:42 +0400 [thread overview]
Message-ID: <50531832.3050902@mvista.com> (raw)
In-Reply-To: <1347616403-3413-1-git-send-email-navinp@cdac.in>
Hello.
On 14-09-2012 13:53, navin patidar wrote:
> stub_device_reset should set kernel thread pointers to NULL.
> so that at the time of usbip_host removal stub_shoutdown_connection
> doesn't try to kill kernel threads which are already killed.
> Signed-off-by: navin patidar <navinp@cdac.in>
> ---
> drivers/staging/usbip/stub_dev.c | 14 +++++++++-----
> 1 file changed, 9 insertions(+), 5 deletions(-)
> diff --git a/drivers/staging/usbip/stub_dev.c b/drivers/staging/usbip/stub_dev.c
> index 92ced35..f584af8 100644
> --- a/drivers/staging/usbip/stub_dev.c
> +++ b/drivers/staging/usbip/stub_dev.c
> @@ -192,16 +192,13 @@ static void stub_shutdown_connection(struct usbip_device *ud)
> if (ud->tcp_tx)
> kthread_stop_put(ud->tcp_tx);
>
> - /*
> - * 2. close the socket
> + /* 2. close the socket
It's the preferred comment style -- why modify it?
> *
> * tcp_socket is freed after threads are killed so that usbip_xmit does
> * not touch NULL socket.
> */
> - if (ud->tcp_socket) {
> + if (ud->tcp_socket)
> sock_release(ud->tcp_socket);
> - ud->tcp_socket = NULL;
> - }
>
> /* 3. free used data */
> stub_device_cleanup_urbs(sdev);
> @@ -233,6 +230,13 @@ static void stub_device_reset(struct usbip_device *ud)
>
> dev_dbg(&udev->dev, "device reset");
>
> + /*reset tcp socket*/
Add spaces after /* and before */, please.
> + ud->tcp_socket = NULL;
> +
> + /*reset kernel thread pointers */
Here too.
WBR, Sergei
next prev parent reply other threads:[~2012-09-14 11:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 9:53 [PATCH] staging: usbip: stub_dev: Fixed oops during removal of usbip_host navin patidar
2012-09-14 11:42 ` Sergei Shtylyov [this message]
2012-09-14 12:04 ` Sebastian Andrzej Siewior
2012-09-14 14:29 ` navin patidar
[not found] ` <CAPV97yfV27x8hB2WUCVmGWEU7i21Y5K5trig2fzQBx+VB_Yk2g@mail.gmail.com>
2012-09-14 14:16 ` Sergei Shtylyov
2012-09-17 12:19 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2012-09-14 13:21 navin patidar
2012-09-14 14:16 ` Dan Carpenter
2012-09-14 14:28 ` Sebastian Andrzej Siewior
2012-09-14 14:41 ` Dan Carpenter
2012-09-18 4:00 navin patidar
2012-09-18 7:40 ` Dan Carpenter
2012-09-18 9:32 ` navin patidar
2012-09-18 9:36 ` Dan Carpenter
2012-09-18 11:44 ` navin patidar
2012-09-18 13:15 ` Dan Carpenter
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=50531832.3050902@mvista.com \
--to=sshtylyov@mvista.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mfm@muteddisk.com \
--cc=navinp@cdac.in \
/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