[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080105212634.GM27894@ZenIV.linux.org.uk>
Date: Sat, 5 Jan 2008 21:26:34 +0000
From: Al Viro <viro@...IV.linux.org.uk>
To: Arjan van de Ven <arjan@...ux.intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
NetDev <netdev@...r.kernel.org>
Subject: Re: Top 10 kernel oopses for the week ending January 5th, 2008
On Sat, Jan 05, 2008 at 01:06:17PM -0800, Arjan van de Ven wrote:
> Rank 3: d_splice_alias
> NULL pointer deref
> Reported 3 times
> Happens in the isofs code
> Only seen in 2.6.24-rc5-mm1
> More info: http://www.kerneloops.org/search.php?search=d_splice_alias
in -rc6-mm1 as well, fixes on l-k...
> Rank 8: evdev_disconnect
> kernel page fault
> Reported 2 times (10 total reports)
> Previously seen in older kernels including 2.6.21 but as far back as
> 2.6.16
> More info:
> http://www.kerneloops.org/search.php?search=evdev_disconnect
Practically certain to be fixed by 6addb1d6de1968b84852f54561cc9a999909b5a9;
it's list_for_each_entry() walking from the entry that just got list_del()
and kernels without that sucker have no protection of the list in question
whatsoever.
> Rank 9: mutex_lock
> kernel null pointer due to rfcomm_tty_close sysfs interaction
> Reported 2 times (9 total reports)
> Ranked 9th last week as well
> More info: http://www.kerneloops.org/search.php?search=mutex_lock
pissfs locking problems; AFAICS, its sysfs_get_dentry() walking into
already unlinked sysfs directory node on the way to target; no exclusion
against that is there and it's not trivial to add.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists