From: Andrew Morton <akpm@linux-foundation.org>
To: Greg KH <greg@kroah.com>
Cc: Arjan van de Ven <arjan@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Jeff Garzik <jeff@garzik.org>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Top kernel oopses/warnings for the week of Friday June 6th, 2008
Date: Sat, 7 Jun 2008 21:55:30 -0700 [thread overview]
Message-ID: <20080607215530.8ad82a7b.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080608043405.GC21251@kroah.com>
On Sat, 7 Jun 2008 21:34:05 -0700 Greg KH <greg@kroah.com> wrote:
> On Fri, Jun 06, 2008 at 11:58:16AM -0700, Arjan van de Ven wrote:
> >
> > Rank 4: sysfs_add_one (warning)
> > Reported 242 times (992 total reports)
> > Duplicate sysfs registration in various components. We don't seem to be
> > making progress on this
> > one unfortunately.
> > This warning was last seen in version 2.6.26-rc3, and first seen in
> > 2.6.24-rc6.
> > More info: http://www.kerneloops.org/searchweek.php?search=sysfs_add_one
>
> I really think this is solved for the USB subsystem at the least. This
> will be hit by other code under development at times, when the developer
> gets something wrong.
For the sysfs vfs caches, yes. But for sysfs pagecache (which I expect
is only symlinks?) the pages will still be on the LRU?
prev parent reply other threads:[~2008-06-08 4:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 18:58 Arjan van de Ven
2008-06-06 20:37 ` Thomas Gleixner
2008-06-06 20:55 ` Arjan van de Ven
2008-06-06 21:06 ` Thomas Gleixner
2008-06-08 4:34 ` Greg KH
2008-06-08 4:55 ` Andrew Morton [this message]
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=20080607215530.8ad82a7b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=greg@kroah.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--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®