From: Frans Pop <elendil@planet.nl>
To: Sven Geggus <lists@fuchsschwanzdomain.de>
Cc: linux-kernel@vger.kernel.org, Mel Gorman <mel@csn.ul.ie>,
linux-mm@kvack.org,
Kernel Testers List <kernel-testers@vger.kernel.org>
Subject: Re: Kernel crash on 2.6.31.x (kcryptd: page allocation failure..)
Date: Sat, 17 Oct 2009 22:30:11 +0200 [thread overview]
Message-ID: <200910172230.13162.elendil@planet.nl> (raw)
In-Reply-To: <hbd4dk$5ac$1@ultimate100.geggus.net>
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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next parent reply other threads:[~2009-10-17 20:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <hbd4dk$5ac$1@ultimate100.geggus.net>
2009-10-17 20:30 ` Frans Pop [this message]
[not found] ` <hbd9v8$7rf$1@ultimate100.geggus.net>
2009-10-18 23:41 ` Frans Pop
2009-10-20 19:16 ` Sven Geggus
2009-10-20 20:02 ` Mel Gorman
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=200910172230.13162.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lists@fuchsschwanzdomain.de \
--cc=mel@csn.ul.ie \
/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