linux-kernel - Re: [PATCH] evdev: Release eventual input device grabs when getting disconnected

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 30 Mar 2008 15:35:13 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Greg KH <greg@...ah.com>
cc:	Bj?rn Steinbrink <B.Steinbrink@....de>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Arjan van de Ven <arjan@...ux.intel.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Johannes Berg <johannes@...solutions.net>,
	Jiri Kosina <jkosina@...e.cz>
Subject: Re: [PATCH] evdev: Release eventual input device grabs when getting
 disconnected



On Sun, 30 Mar 2008, Greg KH wrote:
> 
> I haven't heard of the opposite happening.  Anything that I can try to
> test for here, I have a lot of removable input devices to test with.

Ahh, you weren't cc'd earlier, and may have missed the discussion. It's on 
Linux-kernel in the thread called "Oops/Warning report for the week of 
March 28th 2008"

Johannes says this triggers for him:

	On the other hand, it should be easily reproducible by anyone else with
	the same trick, here's what I do:
	
	 * configure X to use /dev/input/event* devices
	 * in an xterm, do something like
	      rmmod usbhid ; modprobe usbhid
	 * switch to a VT
	 * watch kernel crash as X releases the grab on the event device

and I haven't tried it because none of my normal machines use modules, and 
I was lazy and really hoping somebody else who actually knows the device 
and input layers would take a peek.

		Linus


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/