From: Dmitry Torokhov <dtor@insightbb.com>
To: Greg KH <gregkh@suse.de>
Cc: Dave Young <hidave.darkstar@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] atkbd: cleanup only once
Date: Wed, 27 Jun 2007 00:59:32 -0400 [thread overview]
Message-ID: <200706270059.33550.dtor@insightbb.com> (raw)
In-Reply-To: <20070627042820.GC13513@suse.de>
On Wednesday 27 June 2007 00:28, Greg KH wrote:
> On Wed, Jun 27, 2007 at 12:34:09AM -0400, Dmitry Torokhov wrote:
> > Hi Dave,
> >
> > On Wednesday 27 June 2007 06:59, Dave Young wrote:
> > > Hi,
> > >
> > > If you press ctrl+alt+del several times as kernel booting (before user level bootin), the kernel will oops. I found the ps2_command is called more than once, then the ps2dev->serio maybe NULL pointer.
> > >
> > > 2.6.22-rc5 and 2.6.22-rc6 have same result.
> > >
> > > Signed-off-by: Dave Young <hidave.darkstar@gmail.com>
> > > ---
> > > diff -upr linux/drivers/input/keyboard/atkbd.c linux.new/drivers/input/keyboard/atkbd.c
> > > --- linux/drivers/input/keyboard/atkbd.c 2007-06-27 10:38:37.000000000 +0000
> > > +++ linux.new/drivers/input/keyboard/atkbd.c 2007-06-27 10:37:39.000000000 +0000
> > > @@ -795,6 +795,11 @@ static int atkbd_activate(struct atkbd *
> > >
> > > static void atkbd_cleanup(struct serio *serio)
> > > {
> > > + static int flag;
> > > +
> > > + if(flag)
> > > + return;
> > > + flag = 1;
> >
> > Unfortunately this will prevent atkbd from resetting keyboard on 2nd
> > suspend attempt. It will also not work if you have an active MUX and
> > have a couple of keyboards connected.
> >
> > Greg, now that you removed rwsem from subsystem (and subsystem itself
> > for that matter) there is nothing as far as I can see that stops
> > several threads from running device_shutdown() simultaneously. I also
> > do not see what would isolate device probing and shutting them down
> > at the same time. Am I missing something?
>
> There was never anything stopping that from happening before. No driver
> core code was using that rwsem, so it wasn't protecting anything,
> despite people trying to use it as if it was :)
>
It did protect device_shutdown() from itself, didn't it?
--
Dmitry
next prev parent reply other threads:[~2007-06-27 4:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 10:59 [PATCH] atkbd: cleanup only once Dave Young
2007-06-27 3:01 ` dave young
2007-06-27 4:34 ` Dmitry Torokhov
2007-06-27 4:28 ` Greg KH
2007-06-27 4:59 ` Dmitry Torokhov [this message]
2007-06-27 5:02 ` dave young
2007-06-28 5:18 ` Dmitry Torokhov
2007-06-28 6:12 ` dave young
2007-06-27 5:27 ` Greg KH
2007-06-27 13:37 ` Dmitry Torokhov
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=200706270059.33550.dtor@insightbb.com \
--to=dtor@insightbb.com \
--cc=gregkh@suse.de \
--cc=hidave.darkstar@gmail.com \
--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