From: Johannes Berg <johannes@sipsolutions.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Arjan van de Ven <arjan@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
NetDev <netdev@vger.kernel.org>, Dmitry Torokhov <dtor@mail.ru>
Subject: Re: Oops/Warning report for the week of March 28th 2008
Date: Fri, 28 Mar 2008 22:43:01 +0100 [thread overview]
Message-ID: <1206740581.22530.83.camel@johannes.berg> (raw)
In-Reply-To: <alpine.LFD.1.00.0803281418570.14670@woody.linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]
> > That I've seen before, analysed a bit and posted:
> > http://permalink.gmane.org/gmane.linux.kernel.input/4281
>
> Ahh.. And this is presumably triggered either by some new Xorg behavior in
> fc9 or just the scheduler timing changes that caused other things too?
I tend to think it's actually a regression, I've done exactly what I
described there dozens of times before on older kernels and it doesn't
seem to be a race condition, X always locks the input device and I never
had trouble with that before.
> Your suggested solution sounds ok, but I'm also wondering why those things
> aren't properly refcounted? It does sound like a bug to free the thing
> before all users are gone - regardless of anything else. Hmm?
I have to admit to not understanding the depths of the input code, I
just took a quick look when I posted that. Mind you, that was 5 weeks
ago!
> But the ungrab sounds like the best short-term fix. Do we have a patch for
> testing? Please? It's pretty late in the 2.6.25 cycle for these kinds of
> things..
I don't. I think Dmitry just said in the other mail that he did, but I
haven't seen that yet.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2008-03-28 21:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 18:55 Arjan van de Ven
2008-03-28 20:21 ` Linus Torvalds
2008-03-28 20:51 ` Linus Torvalds
2008-03-28 21:01 ` Johannes Berg
2008-03-28 21:24 ` Linus Torvalds
2008-03-28 21:43 ` Johannes Berg [this message]
2008-03-28 22:01 ` Linus Torvalds
2008-03-28 22:14 ` Jiri Kosina
2008-03-28 22:14 ` Johannes Berg
2008-03-28 21:16 ` Dmitry Torokhov
2008-03-29 12:20 ` Björn Steinbrink
2008-03-28 20:57 ` Björn Steinbrink
2008-03-28 22:33 ` Arjan van de Ven
2008-03-28 22:58 ` Arjan van de Ven
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=1206740581.22530.83.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=arjan@linux.intel.com \
--cc=dtor@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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
all inboxes | Powered by JetHome®