From: Oliver Neukum <oliver@neukum.org>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Gabriel C <nix.or.die@googlemail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [GIT] HID updates for 2.6.29
Date: Wed, 7 Jan 2009 12:30:44 +0100 [thread overview]
Message-ID: <200901071230.45993.oliver@neukum.org> (raw)
In-Reply-To: <alpine.LNX.1.10.0901071049400.5377@jikos.suse.cz>
Am Wednesday 07 January 2009 11:22:27 schrieb Jiri Kosina:
> On Wed, 7 Jan 2009, Gabriel C wrote:
> I believe this is caused by forgotten assignment in usb_register_dev()
> error handling introduced in 079034073fa (added Oliver to CC).
Yes, it seem I caused this. Sorry.
> Commit 079034073fa ("HID: hiddev cleanup -- handle all error conditions
> properly") by mistake removed proper initialization of hid->hiddev pointer
> in hiddev_connect() in case usb_register_dev() succeeds for the hiddev node.
> Put it properly back in place.
>
> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
> ---
> drivers/hid/usbhid/hiddev.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/hid/usbhid/hiddev.c b/drivers/hid/usbhid/hiddev.c
> index 6a98f9f..1928e8a 100644
> --- a/drivers/hid/usbhid/hiddev.c
> +++ b/drivers/hid/usbhid/hiddev.c
> @@ -885,6 +885,7 @@ int hiddev_connect(struct hid_device *hid, unsigned int force)
> } else {
> hid->minor = usbhid->intf->minor;
> hiddev_table[usbhid->intf->minor - HIDDEV_MINOR_BASE] = hiddev;
> + hid->hiddev = hiddev;
It seems to me that this is still a race condition. What prevents open()
from being called before this is set?
Regards
Oliver
next prev parent reply other threads:[~2009-01-07 11:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-04 0:58 [GIT] HID updates for 2.6.29 Jiri Kosina
2009-01-05 9:55 ` Jiri Kosina
2009-01-06 23:50 ` Gabriel C
2009-01-07 0:57 ` Linus Torvalds
2009-01-07 10:22 ` Jiri Kosina
2009-01-07 11:30 ` Oliver Neukum [this message]
2009-01-07 12:25 ` Jiri Kosina
2009-01-07 13:25 ` Gabriel C
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=200901071230.45993.oliver@neukum.org \
--to=oliver@neukum.org \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=nix.or.die@googlemail.com \
--cc=torvalds@linux-foundation.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