linux-kernel - Re: bug in 2.6.26-rc9: sleeping function called from invalid context at kernel/rwsem:21

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <19f34abd0807100234n46e2229ej5077d8c91d08e9f6@mail.gmail.com>
Date:	Thu, 10 Jul 2008 11:34:54 +0200
From:	"Vegard Nossum" <vegard.nossum@...il.com>
To:	"Giacomo A. Catenazzi" <cate@...eee.net>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: bug in 2.6.26-rc9: sleeping function called from invalid context at kernel/rwsem:21

On Thu, Jul 10, 2008 at 10:19 AM, Giacomo A. Catenazzi <cate@...eee.net> wrote:
> Hello,
>
> yesterday at shutdown I had a crash. Unfortunately it seems
> that there was one (or more) oops missing. The bug appeared
> at unmounting partition at shutdown, so there are no logs
> of the previous messages.

Thanks for the report.

It would be really useful to know which filesystems you are/were
using, including virtual filesystems like sysfs. Maybe you are using
ecryptfs or FUSE?

(It would also be interesting to see if you could run
/etc/rc0.d/S40umountfs while the machine is up, to see if you can get
the segfault but keep the machine usable enough to get the whole log.)

Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036
--
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/