From: Grant Grundler <grundler@parisc-linux.org>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Jeroen Roovers <jer@gentoo.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-parisc@vger.kernel.org, Jiri Slaby <jslaby@suse.cz>
Subject: Re: 2.6.28-rc2: USB/INPUT: slab error in cache_alloc_debugcheck_after(): double free?
Date: Sat, 1 Nov 2008 11:56:52 -0600 [thread overview]
Message-ID: <20081101175652.GH13302@colo.lackof.org> (raw)
In-Reply-To: <alpine.LNX.1.10.0810311626160.31273@jikos.suse.cz>
On Fri, Oct 31, 2008 at 04:27:48PM +0100, Jiri Kosina wrote:
> On Fri, 31 Oct 2008, Jeroen Roovers wrote:
>
> > > Could you please provide your config? I am still not able to reproduce
> > > it here. Thanks.
> > Added to the bug report[1]. The architecture is hppa (parisc).
>
> Hmm, so we have just two reports of this corruption, and both of them come
> from PA-RISC systems. Noone else has reported this, and I haven't been
> able to reproduce it myself on x86.
>
> On the other hand I don't seem to see any commit that went into
> arch/parisc between .27 and 28-rc1 which could possibly cause this...
Maybe check drivers/parisc/?
Long shot but if it's easy to check...
Any chance this is a big endian vs little endian problem?
I've found at least one of those in the USB layer before.
grant
next prev parent reply other threads:[~2008-11-01 17:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 23:11 2.6.28-rc2: USB/INPUT: slab error in cache_alloc_debugcheck_after(): double free? Helge Deller
2008-10-31 1:10 ` Jiri Kosina
2008-10-31 2:09 ` Jiri Kosina
2008-10-31 3:45 ` Jeroen Roovers
2008-10-31 11:55 ` Jiri Kosina
2008-10-31 15:16 ` Jeroen Roovers
2008-10-31 15:27 ` Jiri Kosina
2008-11-01 17:56 ` Grant Grundler [this message]
2008-10-31 13:41 ` Jiri Kosina
2008-10-31 19:45 ` Jiri Slaby
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=20081101175652.GH13302@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=jer@gentoo.org \
--cc=jkosina@suse.cz \
--cc=jslaby@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.