From: Dave Jones <davej@codemonkey.org.uk>
To: Adrian Bunk <bunk@kernel.org>
Cc: Arjan van de Ven <arjan@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
NetDev <netdev@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jeff Garzik <jgarzik@pobox.com>
Subject: Re: Top kernel oopses/warnings for the week of May 16th 2008
Date: Mon, 19 May 2008 23:53:48 -0400 [thread overview]
Message-ID: <20080520035348.GA32472@codemonkey.org.uk> (raw)
In-Reply-To: <20080516180426.GA3284@cs181133002.pp.htv.fi>
On Fri, May 16, 2008 at 09:04:26PM +0300, Adrian Bunk wrote:
> On Fri, May 16, 2008 at 09:41:31AM -0700, Arjan van de Ven wrote:
> >...
> > Bug of the week
> > ---------------
> > Not in the top 10 (but barely not so), but upcoming fast is a bug that has a very
> > distinct pattern.
> > The backtraces are at http://www.kerneloops.org/searchweek.php?search=fput
> >
> > The pattern is that the kernel gets an invalid pointer passed to fput(),
> > coming down from a select() system call done by the "wpa_supplicant" program.
> > The fact that it is ONLY wpa_supplicant implicates the wireless/network stack.
> > Another observation is that this only happens with 64 bit kernels, even though
> > a large portion of the users uses 32 bit kernels. This implies that this is a 64-bit
> > type of bug. It appears that the top 32 bit of the pointers is getting corrupted
> > (the bottom part at least looks valid).
> >...
>
> Unless I misunderstand your webinterface another pattern is a "fc9" in
> the version string.
Unsurprising really given we just did a release, and not many other distros
are enabling kerneloops by default yet.
> My first guess would be that it might be a problem in some code that is
> only in Fedora kernels?
Very likely, though it's worth noting that all the wireless patches we have
in f9 are from wireless.git, so they're valid 2.6.26-rc bugs
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2008-05-20 3:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 16:41 Top kernel oopses/warnings for the week of May 16th 2008 Arjan van de Ven
2008-05-16 17:14 ` Evgeniy Polyakov
2008-05-16 18:04 ` Adrian Bunk
2008-05-16 18:19 ` Arjan van de Ven
2008-05-20 3:53 ` Dave Jones [this message]
2008-05-16 18:50 ` notification for systemtap-related oops Frank Ch. Eigler
2008-05-16 19:47 ` Arjan van de Ven
2008-05-16 20:23 ` Frank Ch. Eigler
[not found] <fa.LFS/TATb5YijFetLw6A+gczrVAQ@ifi.uio.no>
2008-05-17 1:55 ` Top kernel oopses/warnings for the week of May 16th 2008 Robert Hancock
2008-05-17 14:12 ` Andrea Arcangeli
2008-05-17 14:57 ` Arjan van de Ven
2008-05-17 20:34 ` Andrea Arcangeli
2008-05-17 17:38 ` Robert Hancock
[not found] <fa.d+EaKQa5MirlzoI/uZKGy3xe0h0@ifi.uio.no>
[not found] ` <fa.TM0B9DZ+uvPYd9hbDhfuRgtReEk@ifi.uio.no>
[not found] ` <fa.aEHVuArwNEvL0BbdjUyZdMtgx5s@ifi.uio.no>
[not found] ` <fa.Td5KtiJWRKP94D9KrvGd+GkHdW0@ifi.uio.no>
[not found] ` <fa.wtWnOZVeQ06/16BVE5ml7FVHP+c@ifi.uio.no>
2008-05-19 2:23 ` Robert Hancock
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=20080520035348.GA32472@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=bunk@kernel.org \
--cc=jgarzik@pobox.com \
--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 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.