From: Greg KH <gregkh@suse.de>
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>,
Netdev <netdev@vger.kernel.org>,
linux-wireless@vger.kernel.org, Samuel Ortiz <samuel@sortiz.org>,
Andrey Borzenkov <arvidjaar@mail.ru>,
Bjorn Helgaas <bjorn.helgaas@hp.com>,
Stephen Smalley <sds@tycho.nsa.gov>,
James Morris <jmorris@namei.org>,
Eric Paris <eparis@parisplace.org>, Ingo Molnar <mingo@elte.hu>,
Paulo Pereira <pfmp.404@gmail.com>,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [2/2] 2.6.22-rc4: known regressions with patches v3
Date: Wed, 13 Jun 2007 13:35:02 -0700 [thread overview]
Message-ID: <20070613203501.GA5708@suse.de> (raw)
In-Reply-To: <46704C4D.5010803@googlemail.com>
On Wed, Jun 13, 2007 at 09:58:05PM +0200, Michal Piotrowski wrote:
> USB
>
> Subject : list_add corruption. prev->next should be next (f7d28794), but
> was f0df8ed4 (prev=f0df8ed4) Kernel Bug at lib/list_debug.c:33
> References : http://bugzilla.kernel.org/show_bug.cgi?id=8561
> Submitter : Paulo Pereira <pfmp.404@gmail.com>
> Handled-By : Alan Stern <stern@rowland.harvard.edu>
> Patch : http://bugzilla.kernel.org/show_bug.cgi?id=8561#c8
> Status : patch was suggested
I'm pretty sure this wasn't a "regression" and was always there, and
that the proposed patch did fix the solution, right Paulo and Alan?
thanks,
greg k-h
next prev parent reply other threads:[~2007-06-13 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <46704B5D.5020106@googlemail.com>
[not found] ` <46704B5D.5020106-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2007-06-13 19:58 ` [2/2] 2.6.22-rc4: known regressions with patches v3 Michal Piotrowski
2007-06-13 20:35 ` Greg KH [this message]
2007-06-14 7:57 ` Paulo Pereira
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=20070613203501.GA5708@suse.de \
--to=gregkh@suse.de \
--cc=akpm@linux-foundation.org \
--cc=arvidjaar@mail.ru \
--cc=bjorn.helgaas@hp.com \
--cc=eparis@parisplace.org \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=pfmp.404@gmail.com \
--cc=samuel@sortiz.org \
--cc=sds@tycho.nsa.gov \
--cc=stern@rowland.harvard.edu \
--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;
as well as URLs for NNTP newsgroup(s).