From: Shuah Khan <shuah@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: valentina.manea.m@gmail.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH] usbip: usbip_host: fix bad unlock balance during stub_probe()
Date: Wed, 16 May 2018 08:03:10 -0600 [thread overview]
Message-ID: <0fd916b1-ff46-a755-5198-06899f8211f6@kernel.org> (raw)
In-Reply-To: <20180516054909.GB29964@kroah.com>
On 05/15/2018 11:49 PM, Greg KH wrote:
> On Tue, May 15, 2018 at 05:57:23PM -0600, Shuah Khan (Samsung OSG) wrote:
>> stub_probe() calls put_busid_priv() in an error path when device isn't
>> found in the busid_table. Fix it by making put_busid_priv() safe to be
>> called with null struct bus_id_priv pointer.
>>
>> This problem happens when "usbip bind" is run without loading usbip_host
>> driver and then running modprobe. The first failed bind attempt unbinds
>> the device from the original driver and when usbip_host is modprobed,
>> stub_probe() runs and doesn't find the device in its busid table and calls
>> put_busid_priv(0 with null bus_id_priv pointer.
>>
>> usbip-host 3-10.2: 3-10.2 is not in match_busid table... skip!
>>
>> [ 367.359679] =====================================
>> [ 367.359681] WARNING: bad unlock balance detected!
>> [ 367.359683] 4.17.0-rc4+ #5 Not tainted
>> [ 367.359685] -------------------------------------
>> [ 367.359688] modprobe/2768 is trying to release lock (
>> [ 367.359689]
>> ==================================================================
>> [ 367.359696] BUG: KASAN: null-ptr-deref in
>> print_unlock_imbalance_bug+0x99/0x110
>> [ 367.359699] Read of size 8 at addr 0000000000000058 by task
>> modprobe/2768
>
> Minor nit, no need to line-wrap this.
>
>> [ 367.359705] CPU: 4 PID: 2768 Comm: modprobe Not tainted 4.17.0-rc4+ #5
>>
>> Fixes: 22076557b07c ("usbip: usbip_host: fix NULL-ptr deref and
>> use-after-free errors") in usb-linus
>
> Nor this, and the extra blank line isn't needed here either. I'll fix
> it up by hand when I queue this up later today, thanks.
>
Thanks. I will keep that in mind the next time.
thanks,
-- Shuah
prev parent reply other threads:[~2018-05-16 14:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 23:57 Shuah Khan (Samsung OSG)
2018-05-16 5:49 ` Greg KH
2018-05-16 14:03 ` Shuah Khan [this message]
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=0fd916b1-ff46-a755-5198-06899f8211f6@kernel.org \
--to=shuah@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=valentina.manea.m@gmail.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
all inboxes | Powered by JetHome®