mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>, Adrian Bunk <bunk@stusta.de>,
	Patrick Caulfield <pcaulfie@redhat.com>,
	David Teigland <teigland@redhat.com>,
	bluez-devel@lists.sourceforge.net,
	Marcel Holtmann <marcel@holtmann.org>,
	Jiri Kosina <jkosina@suse.cz>,
	Dmitry Torokhov <dtor@insightbb.com>
Subject: Re: 2.6.22-rc7: known regressions with patches v2
Date: Sat, 07 Jul 2007 12:23:11 -0400	[thread overview]
Message-ID: <1183825391.3066.59.camel@shinybook.infradead.org> (raw)
In-Reply-To: <468FBA20.8060509@googlemail.com>

On Sat, 2007-07-07 at 18:06 +0200, Michal Piotrowski wrote:
> FBDEV
> 
> Subject         : SLUB kmalloc-32768: Poison check failed@0xc1e20000
> slab 0xc04de400
> References      : http://lkml.org/lkml/2007/7/4/305
> Last known good : ?
> Submitter       : David Woodhouse <dwmw2@infradead.org>
> Caused-By       : ?
> Handled-By      : ?
> Status          : unknown

If you're looking for someone to blame, consider the fact that this has
gone away now I've switched back to slab. :)

> Bluetooth
> 
> Subject         : problem with a bluetooth mouse
> References      : http://lkml.org/lkml/2007/7/4/321
> Last known good : ?
> Submitter       : David Woodhouse <dwmw2@infradead.org>
> Caused-By       : ?
> Handled-By      : Jiri Kosina <jkosina@suse.cz>
>                   Dmitry Torokhov <dtor@insightbb.com>
> Patch           : http://lkml.org/lkml/2007/7/6/391
> Status          : patch available

That patch was a straw man for Marcel to comment on, not necessarily a
real fix. I don't know the code that well, and naïvely reordering bits
of it could have introduced another race which I just haven't triggered
yet.

Strictly speaking, it wasn't a 2.6.22 regression either -- I actually
saw it for the first time in 2.6.21-rc iirc.

Thanks for tracking these, btw. It's very useful.

-- 
dwmw2


  reply	other threads:[~2007-07-07 16:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-07 16:06 Michal Piotrowski
2007-07-07 16:23 ` David Woodhouse [this message]
2007-07-07 16:59   ` Michal Piotrowski
2007-07-07 23:07     ` Christoph Lameter
2007-07-07 23:38       ` Linus Torvalds

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=1183825391.3066.59.camel@shinybook.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=bunk@stusta.de \
    --cc=dtor@insightbb.com \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=pcaulfie@redhat.com \
    --cc=teigland@redhat.com \
    --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®