From: Shuah Khan <skhan@linuxfoundation.org>
To: Tom Seewald <tseewald@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: syzbot+a93fba6d384346a761e3@syzkaller.appspotmail.com,
Valentina Manea <valentina.manea.m@gmail.com>,
Shuah Khan <shuah@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
stable@vger.kernel.org
Subject: Re: [PATCH 1/4] usbip: add sysfs_lock to synchronize sysfs code paths
Date: Fri, 16 Apr 2021 15:43:45 -0600 [thread overview]
Message-ID: <ea81015d-79f3-f22e-0b96-e0ae58acfc14@linuxfoundation.org> (raw)
In-Reply-To: <20210416205319.14075-1-tseewald@gmail.com>
On 4/16/21 2:53 PM, Tom Seewald wrote:
> From: Shuah Khan <skhan@linuxfoundation.org>
>
> commit 4e9c93af7279b059faf5bb1897ee90512b258a12 upstream.
>
> Fuzzing uncovered race condition between sysfs code paths in usbip
> drivers. Device connect/disconnect code paths initiated through
> sysfs interface are prone to races if disconnect happens during
> connect and vice versa.
>
> This problem is common to all drivers while it can be reproduced easily
> in vhci_hcd. Add a sysfs_lock to usbip_device struct to protect the paths.
>
> Use this in vhci_hcd to protect sysfs paths. For a complete fix, usip_host
> and usip-vudc drivers and the event handler will have to use this lock to
> protect the paths. These changes will be done in subsequent patches.
>
> Cc: stable@vger.kernel.org # 4.9.x
> Reported-and-tested-by: syzbot+a93fba6d384346a761e3@syzkaller.appspotmail.com
> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
> Link: https://lore.kernel.org/r/b6568f7beae702bbc236a545d3c020106ca75eac.1616807117.git.skhan@linuxfoundation.org
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Signed-off-by: Tom Seewald <tseewald@gmail.com>
> ---
> drivers/usb/usbip/usbip_common.h | 3 +++
> drivers/usb/usbip/vhci_hcd.c | 1 +
> drivers/usb/usbip/vhci_sysfs.c | 30 +++++++++++++++++++++++++-----
> 3 files changed, 29 insertions(+), 5 deletions(-)
>
Thank you for the backport.
Reviewed-by: Shuah Khan <skhan@linuxfoundation.org>
Greg, please pick this up for 4.9.x
thanks,
-- Shuah
next prev parent reply other threads:[~2021-04-16 21:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 20:53 [PATCH 1/4] usbip: add sysfs_lock to synchronize sysfs code paths Tom Seewald
2021-04-16 20:53 ` [PATCH 2/4] usbip: stub-dev " Tom Seewald
2021-04-16 21:44 ` Shuah Khan
2021-04-16 20:53 ` [PATCH 3/4] usbip: vudc " Tom Seewald
2021-04-16 21:45 ` Shuah Khan
2021-04-16 20:53 ` [PATCH 4/4] usbip: synchronize event handler with " Tom Seewald
2021-04-16 21:45 ` Shuah Khan
2021-04-16 21:43 ` Shuah Khan [this message]
2021-04-19 12:23 ` [PATCH 1/4] usbip: add sysfs_lock to synchronize " Greg Kroah-Hartman
2021-04-19 21:42 ` Shuah Khan
2021-04-20 7:30 ` Greg Kroah-Hartman
[not found] <cover.1616807117.git.skhan@linuxfoundation.org>
2021-03-30 1:36 ` Shuah Khan
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=ea81015d-79f3-f22e-0b96-e0ae58acfc14@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--cc=syzbot+a93fba6d384346a761e3@syzkaller.appspotmail.com \
--cc=tseewald@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).