From: Frans Pop <elendil@planet.nl>
To: Sven Geggus <lists@fuchsschwanzdomain.de>
Subject: Re: Kernel crash on 2.6.31.x (kcryptd: page allocation failure..)
Date: Sat, 17 Oct 2009 22:30:11 +0200
User-Agent: KMail/1.9.9
Cc: linux-kernel@vger.kernel.org, Mel Gorman <mel@csn.ul.ie>,
       linux-mm@kvack.org,
       Kernel Testers List <kernel-testers@vger.kernel.org>
References: <hbd4dk$5ac$1@ultimate100.geggus.net>
In-reply-To: <hbd4dk$5ac$1@ultimate100.geggus.net>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200910172230.13162.elendil@planet.nl>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1199
Lines: 32

Hello Sven,

Sven Geggus wrote:
> I can reproducible crash my machine by writing bulk data from a
> socket to an encrypted partition. It always crashes after a few
> Gigabytes have been written.
> 
> The Partition in charge is using dm-crypt+xfs filesystem.

This is without any doubt related to an issue that's already being 
investigated. I have to warn you that the thread is very long:

http://thread.gmane.org/gmane.linux.kernel/896714

What is the _exact_ command sequence you use to reproduce it? I already 
have a testcase, but a second test case, or a simpler one, may be useful.

In all cases reported so far, and also in your case, networking is involved 
in the actual allocation errors.

It would also be useful if you could try to bisect the issue independently. 
For me bisection has proven difficult because the symptoms change 
between .30 and .31. The suspicion is that more than one change is 
involved in the regression.

Cheers,
FJP
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/