From: Mike Snitzer <snitzer@redhat.com>
To: Matthias Dahl <ml_linux-kernel@binary-island.eu>
Cc: linux-mm@kvack.org, dm-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [4.7.0rc6] Page Allocation Failures with dm-crypt
Date: Mon, 11 Jul 2016 09:44:54 -0400 [thread overview]
Message-ID: <20160711134454.GA28370@redhat.com> (raw)
In-Reply-To: <fe0eb105b21013453bc3375e7026925b@mail.ud19.udmedia.de>
On Mon, Jul 11 2016 at 9:27am -0400,
Matthias Dahl <ml_linux-kernel@binary-island.eu> wrote:
> Hello Mike...
>
> On 2016-07-11 15:18, Mike Snitzer wrote:
>
> >Something must explain the execessive nature of your leak but
> >it isn't a known issue.
>
> Since I am currently setting up the new machine, all tests were
> performed w/ various live cd images (Fedora Rawhide, Gentoo, ...)
> and I saw the exact same behavior everywhere.
>
> >Have you tried running with kmemleak enabled?
>
> I would have to check if that is enabled on the live images but even if
> it is, how would that work? The default interval is 10min. If I fire up
> a dd, the memory is full within two seconds or so... and after that, the
> OOM killer kicks in and all hell breaks loose unfortunately.
You can control when kmemleak scans. See Documentation/kmemleak.txt
You could manually trigger a scan just after the dd is started.
But I doubt the livecds have kmemleak compiled into their kernels.
> I don't think this is a particular unique issue on my side. You could,
> if I am right, easily try a Fedora Rawhide image and reproduce it there
> yourself. The only unique point here is my RAID10 which is a Intel Rapid
> Storage s/w RAID. I have no clue if this could indeed cause such a "bug"
> and how.
What is your raid10's full stripesize? Is your dd IO size of 512K
somehow triggering excess R-M-W cycles which is exacerbating the
problem?
--
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 prev parent reply other threads:[~2016-07-11 13:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-09 13:40 [4.7.0rc6] Page Allocation Failures with dm-crypt Matthias Dahl
2016-07-11 8:31 ` Matthias Dahl
2016-07-11 13:18 ` Mike Snitzer
2016-07-11 13:27 ` [dm-devel] " Matthias Dahl
2016-07-11 13:44 ` Mike Snitzer [this message]
2016-07-11 13:30 ` Mike Snitzer
2016-07-11 14:47 ` [dm-devel] " Matthias Dahl
2016-07-12 8:06 ` Matthias Dahl
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=20160711134454.GA28370@redhat.com \
--to=snitzer@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ml_linux-kernel@binary-island.eu \
/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;
as well as URLs for NNTP newsgroup(s).