Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Madhuparna Bhowmik <madhuparnabhowmik10@gmail.com>
Date:   Sat, 4 Apr 2020 23:09:21 +0530
To:     Greg KH <gregkh@linuxfoundation.org>
Cc:     madhuparnabhowmik10@gmail.com, hariprasad.kelam@gmail.com,
        colin.king@canonical.com, linux-usb@vger.kernel.org,
        linux-kernel@vger.kernel.org, ldv-project@linuxtesting.org,
        andrianov@ispras.ru, stern@rowland.harvard.edu
Subject: Re: [PATCH] usb: host: u132-hcd: Remove u132_static_list and list
 head u132_list
Message-ID: <20200404173921.GB19729@madhuparna-HP-Notebook>
References: <20200403181816.8115-1-madhuparnabhowmik10@gmail.com>
 <20200404092308.GB1110038@kroah.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20200404092308.GB1110038@kroah.com>
User-Agent: Mutt/1.9.4 (2018-02-28)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Sat, Apr 04, 2020 at 11:23:08AM +0200, Greg KH wrote:
> On Fri, Apr 03, 2020 at 11:48:16PM +0530, madhuparnabhowmik10@gmail.com wrote:
> > From: Madhuparna Bhowmik <madhuparnabhowmik10@gmail.com>
> > 
> > u132_static_list is a global list protected by u132_module_lock.
> > It is read in the u132_hcd_exit() function without holding the lock
> > thus may lead to data race.
> > However, it turns out that this list isn't used for anything useful
> > and thus it is okay to get rid of it.
> > Thus, remove the u132_static_list from u132-hcd module.
> > Also remove struct list_head u132_list from struct u132.
> > 
> > Found by Linux Driver Verification project (linuxtesting.org).
> > 
> > Suggested-by: Alan Stern <stern@rowland.harvard.edu>
> > Signed-off-by: Madhuparna Bhowmik <madhuparnabhowmik10@gmail.com>
> > ---
> >  drivers/usb/host/u132-hcd.c | 10 ----------
> >  1 file changed, 10 deletions(-)
> 
> Please properly version your patches, otherwise I have no idea what
> changed from the previous one, nor do I know which patch to take over
> which.
> 
> The instructions for how to do this is in the documentation.  Please fix
> up and resend so I have a chance to know what to do...
>
Sure, I will do it.

Thank you,
Madhuparna
> thanks,
> 
> greg k-h