From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Andres Salomon <dilinger@queued.net>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] input: psmouse: fix input_dev leak in lifebook driver
Date: Wed, 16 Jan 2008 14:15:26 -0500 [thread overview]
Message-ID: <20080116141353.ZZRA012@mailhub.coreip.homeip.net> (raw)
In-Reply-To: <20080116125801.199224f3@ephemeral>
On Wed, Jan 16, 2008 at 12:58:01PM -0500, Andres Salomon wrote:
> On Tue, 15 Jan 2008 17:04:01 -0500
> Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
>
> > On Sat, Jan 12, 2008 at 03:12:52PM -0500, Andres Salomon wrote:
> > >
> > > The lifebook driver may register a second input device, but it never
> > > unregisters it. This fixes that.
> > >
> > > Signed-off-by: Andres Salomon <dilinger@debian.org>
> >
> > Applied, thank you Andres.
> >
>
> Hi Dmitry,
>
> There's one additional patch, I don't know if you saw it; the subject
> was "check return value of input_register_device() in hil_ptr.c's init".
>
I have seen it but postponed for later. Right now I am trying to get though
2.6.24 material.
>
> Also, I've found myself needing to provide my own device_attribute for
> the OLPC psmouse driver; I couldn't use PSMOUSE_DEFINE_ATTR(), as its
> set_helper callback calls psmouse_disable.
>
> static DEVICE_ATTR(powered, S_IWUSR | S_IRUGO, hgpk_show_powered,
> hgpk_set_powered);
>
> Unfortunately, in order to not be racy, hgpk_set_powered needs to
> deal with psmouse_mutex. Which method of dealing with this would
> you prefer? I could either make psmouse_mutex no longer static,
> provide psmouse_mutex locking functions (declared in psmouse.h), or
> put psmouse_mutex into 'struct psmouse'. Or, if you have any other
> ideas..
Could you just send me the code? I tend to think better when I see it...
Thanks!
--
Dmitry
prev parent reply other threads:[~2008-01-16 19:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-12 20:12 [PATCH] input: psmouse: fix input_dev leak in lifebook driver Andres Salomon
2008-01-15 22:04 ` Dmitry Torokhov
2008-01-16 17:58 ` Andres Salomon
2008-01-16 19:15 ` Dmitry Torokhov [this message]
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=20080116141353.ZZRA012@mailhub.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=dilinger@queued.net \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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).