linux-kernel - Re: [RPC] OLPC tablet input driver.

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:	Tue, 29 Aug 2006 08:29:13 -0400
From:	"Dmitry Torokhov" <dtor@...ightbb.com>
To:	"Zephaniah E. Hull" <warp@...allh.com>
Cc:	"Arjan van de Ven" <arjan@...radead.org>,
	linux-input@...ey.karlin.mff.cuni.cz, linux-kernel@...r.kernel.org,
	"Marcelo Tosatti" <mtosatti@...hat.com>
Subject: Re: [RPC] OLPC tablet input driver.

On 8/29/06, Zephaniah E. Hull <warp@...allh.com> wrote:
> >
> > also.. there's no locking visible anywhere in the driver... is this
> > right?
>
> It looks like psmouse handles it with a mutex lock around freeing stuff
> and calling the callback function pointers we set on init, so we
> _should_ be safe unless I've missed something.
>
> Add to it that none of the other psmouse drivers are doing locking on
> their own, and I'm fairly sure that this is correct. (But if someone
> knows better, please correct me.)
>

Serio and psmouse cores should handle all necessary locking, no worries here.

-- 
Dmitry
-
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/