From: Valentine Barshak <vbarshak@mvista.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-usb@vger.kernel.org, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] USB: HID: Fix race between disconnect and hiddev_ioctl
Date: Mon, 6 Dec 2010 17:45:19 +0300 [thread overview]
Message-ID: <20101206144519.GA8438@mvista.com> (raw)
If a USB HID device is disconneceted, the hiddev_ioctl could try
to access invalid hiddev->hid pointer.
The following two patches attempt to fix race condition between
disconnect and hiddev_ioctl and make hiddev_ioctl always return
-ENODEV on a disconnected device.
next reply other threads:[~2010-12-06 14:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 14:45 Valentine Barshak [this message]
2010-12-06 14:51 ` [PATCH 1/2] USB: HID: Fix race between disconnect and hiddev_ioctl Valentine Barshak
2010-12-07 14:47 ` Jiri Kosina
2010-12-07 15:02 ` Valentine Barshak
[not found] ` <20101206144519.GA8438-Igf4POYTYCDQT0dZR+AlfA@public.gmane.org>
2010-12-06 15:16 ` [PATCH 2/2] USB: HID: Consolidate device existence checks in hiddev_ioctl Valentine Barshak
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=20101206144519.GA8438@mvista.com \
--to=vbarshak@mvista.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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).