linux-kernel - Re: sleeping function called from invalid context at block/cfq-iosched.c (Was: Re: 2.6.21-mm1)

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: <Pine.LNX.4.61.0705081026160.17280@yvahk01.tjqt.qr>
Date:	Tue, 8 May 2007 10:28:29 +0200 (MEST)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	David Chinner <dgc@....com>
cc:	Jeremy Fitzhardinge <jeremy@...p.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Simon Arlott <simon@...e.lp0.eu>, linux-kernel@...r.kernel.org
Subject: Re: sleeping function called from invalid context at block/cfq-iosched.c
 (Was: Re: 2.6.21-mm1)


On May 8 2007 16:18, David Chinner wrote:
>
>On Mon, May 07, 2007 at 10:38:24PM -0700, Jeremy Fitzhardinge wrote:
>> Andrew Morton wrote:
>> > On Mon, 07 May 2007 21:31:06 -0700 Jeremy Fitzhardinge <jeremy@...p.org> wrote:
>> >   
>> >> I've found that XFS+lvm+4k stacks is completely unusable with current
>> >> kernels.  I get hangs/oopes after ~10mins of work.
>> >
>> > Sounds like this is new behaviour?
>> > I wonder why.  Same compiler version?
>> 
>> I've only recently started using xfs, so I couldn't say if its new
>> behaviour.  I did notice that it took a week or so for problems to set
>> in; my theory is that as the filesystem got a bit aged, its
>> datastructures got a bit more complex, and cause the kernel code to use
>> more stack.  But that's just a guess.

FWIW, I run dm-crypt+xfs on one machine, of course with 8k since that's
suse default. No issues. dm-crypt and lvm got something in common,
don't they?


Jan
-- 
-
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/