From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: John Dykstra <john.dykstra1@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Adrian Bunk <bunk@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Natalie Protasevich <protasnb@gmail.com>,
Kernel Testers List <kernel-testers@vger.kernel.org>,
Network Development <netdev@vger.kernel.org>,
Linux ACPI <linux-acpi@vger.kernel.org>,
Linux PM List <linux-pm@lists.linux-foundation.org>,
Linux SCSI List <linux-scsi@vger.kernel.org>,
Linux Wireless List <linux-wireless@vger.kernel.org>,
DRI <dri-devel@lists.sourceforge.net>
Subject: Re: 2.6.31-rc6-git5: Reported regressions from 2.6.30
Date: Thu, 20 Aug 2009 23:28:24 +0200 [thread overview]
Message-ID: <200908202328.24252.rjw@sisk.pl> (raw)
In-Reply-To: <1250801571.7176.10.camel@Maple>
On Thursday 20 August 2009, John Dykstra wrote:
> On Wed, 2009-08-19 at 22:20 +0200, Rafael J. Wysocki wrote:
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14002
> > Subject : WARNING: at net/ipv4/af_inet.c:154
> > inet_sock_destruct+0x164/0x1c0()
> > Submitter : Ralf Hildebrandt <ralf.hildebrandt@charite.de>
> > Date : 2009-08-18 12:37 (2 days old)
>
> That looks similar to the WARNING discussed in [1].
>
> There was no resolution to that thread. However, [2] points out
> possible other occurrences of the problem in 2.6.27, 28 and 29.
>
> -- John
>
> [1] http://www.spinics.net/lists/netdev/msg103267.html
> [2] http://www.spinics.net/lists/netdev/msg104120.html
Thanks for the information.
So I'll drop this from the list, since it most probably is not a recent thing.
Best,
Rafael
next prev parent reply other threads:[~2009-08-20 21:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 20:20 2.6.31-rc6-git5: Reported regressions from 2.6.30 Rafael J. Wysocki
2009-08-20 20:52 ` John Dykstra
2009-08-20 21:28 ` Rafael J. Wysocki [this message]
2009-08-21 21:34 ` Larry Finger
2009-08-21 22:02 ` Rafael J. Wysocki
2009-08-25 23:25 ` Larry Finger
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=200908202328.24252.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=dri-devel@lists.sourceforge.net \
--cc=john.dykstra1@gmail.com \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=protasnb@gmail.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;
as well as URLs for NNTP newsgroup(s).