mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ajay Kaher <ajay.kaher@samsung.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	AMAN DEEP <aman.deep@samsung.com>,
	HEMANSHU SRIVASTAVA <hemanshu.s@samsung.com>
Subject: FW: RE: Re: Subject: [PATCH v3] USB:Core: BugFix: Proper handling of Race Condition when two USB class drivers try to call init_usb_class simultaneously
Date: Wed, 01 Mar 2017 11:12:04 +0000	[thread overview]
Message-ID: <20170301111204epcms5p393ae97a6265e6d357d17c3370c2ac874@epcms5p3> (raw)
In-Reply-To: <20170222125736epcms5p1eed1cc9c1db3b402a7f7c46df3e04f1a@epcms5p1>

[-- Attachment #1: Type: text/plain, Size: 2757 bytes --]


> On Mon, 22 Feb 2017, Ajay Kaher wrote:
> 
>> On Mon, 20 Feb 2017, Ajay Kaher wrote:
>> 
>>> Alan, as per my understanding I have shifted the lock from
>>> release_usb_class() to destroy_usb_class() in patch v3. 
>>> If it is not right, please explain in detail which race condition
>>> I have missed and also share your suggestions.
>>> 
>> 
>> Have you considered what would happen if destroy_usb_class() ran, but 
>> some other CPU was still holding a reference to usb_class?  And what if 
>> the last reference gets dropped later on, while init_usb_class() is 
>> running?
> 
> Access of usb_class->kref is only from either init_usb_class()
> or destroy_usb_class(), and both these functions are now protected
> with Mutex Locking in patch v3, so there is no chance of race condition
> as per above scenarios.
> 
>> Maybe that's not possible here, but it is possible in general for 
>> refcounted objects.  So yes, this code is probably okay, but it isn't 
>> good form.
> 
> As per my understanding, I found to be one of the best possible solution
> for this problem and this solutiuon don't have any side effect.

Alan, I had shared modified Patch v3 as per your inputs to prevent
the race condition during simultaneously calling of init_usb_class().
If you think there is scope to improve the patch, please share your inputs.

thanks,
ajay kaher


Signed-off-by: Ajay Kaher

---

 drivers/usb/core/file.c |    6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/drivers/usb/core/file.c b/drivers/usb/core/file.c
index 822ced9..a12d184 100644
--- a/drivers/usb/core/file.c
+++ b/drivers/usb/core/file.c
@@ -27,6 +27,7 @@
 #define MAX_USB_MINORS 256
 static const struct file_operations *usb_minors[MAX_USB_MINORS];
 static DECLARE_RWSEM(minor_rwsem);
+static DEFINE_MUTEX(init_usb_class_mutex);

 static int usb_open(struct inode *inode, struct file *file)
 {
@@ -109,8 +110,10 @@ static void release_usb_class(struct kref *kref)

 static void destroy_usb_class(void)
 {
+       mutex_lock(&init_usb_class_mutex);
        if (usb_class)
                kref_put(&usb_class->kref, release_usb_class);
+       mutex_unlock(&init_usb_class_mutex);
 }

 int usb_major_init(void)
@@ -171,7 +174,10 @@ int usb_register_dev(struct usb_interface *intf,
        if (intf->minor >= 0)
                return -EADDRINUSE;

+       mutex_lock(&init_usb_class_mutex);
        retval = init_usb_class();
+       mutex_unlock(&init_usb_class_mutex);
+
        if (retval)
                return retval;

 

  parent reply	other threads:[~2017-03-01 12:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170220192040epcas3p37ded8ece49ed9385df80d3b813a953bc@epcas3p3.samsung.com>
2017-02-22 12:57 ` Ajay Kaher
     [not found]   ` <CGME20170220192040epcas3p37ded8ece49ed9385df80d3b813a953bc@epcms5p3>
2017-03-01 11:12     ` Ajay Kaher [this message]
2017-03-01 15:15       ` FW: " Alan Stern
     [not found]         ` <CGME20170301151552epcas5p3ecf8f7dc55323b2ceaff8c8a9b9644c4@epcms5p1>
2017-03-02  7:49           ` FW: RE: " Ajay Kaher
     [not found]         ` <CGME20170301151552epcas5p3ecf8f7dc55323b2ceaff8c8a9b9644c4@epcms5p2>
2017-03-03 14:49           ` FW: " Ajay Kaher
2017-03-03 16:53             ` Alan Stern
     [not found]               ` <CGME20170303165352epcas5p2c408a284100b5053daf458a4ad4d9337@epcms5p7>
2017-03-07  4:35                 ` Subject: [PATCH v4] " Ajay Kaher
2017-03-07 15:00                   ` Alan Stern
     [not found]                     ` <CGME20170307150103epcas2p348320fdfbb176978d084d8f2b7b9a049@epcms5p7>
2017-03-09 11:34                       ` Ajay Kaher
2017-03-09 12:10                         ` gregkh
     [not found]                         ` <CGME20170307150103epcas2p348320fdfbb176978d084d8f2b7b9a049@epcms5p2>
2017-03-17 10:56                           ` [PATCH v4] USB: " Ajay Kaher
2017-03-23  7:18                             ` gregkh
2017-03-21 14:49                           ` FW: " Ajay Kaher
2017-03-08 18:05                   ` Subject: [PATCH v4] USB:Core: BugFix: " gregkh

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=20170301111204epcms5p393ae97a6265e6d357d17c3370c2ac874@epcms5p3 \
    --to=ajay.kaher@samsung.com \
    --cc=aman.deep@samsung.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hemanshu.s@samsung.com \
    --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®