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:18:19 -0400 [thread overview]
Message-ID: <20160711131818.GA28102@redhat.com> (raw)
In-Reply-To: <e7af885e08e1ced4f75313bfdfda166d@mail.ud19.udmedia.de>
On Mon, Jul 11 2016 at 4:31am -0400,
Matthias Dahl <ml_linux-kernel@binary-island.eu> wrote:
> Hello,
>
> I made a few more tests and here my observations:
>
> - kernels 4.4.8 and 4.5.5 show the same behavior
>
> - the moment dd starts, memory usage spikes rapidly and within a just
> a few seconds has filled up all 32 GiB of RAM
>
> - dd w/ direct i/o works just fine
>
> - mkfs.ext4 unfortunately shows the same behavior as dd w/o direct i/o
> and such makes creation of an ext4 fs on dm-crypt a game of luck
>
> (much more exposed so with e2fsprogs 1.43.1)
>
> I am kind of puzzled that this bug has seemingly gone so long unnoticed
> since it is rather severe and makes dm-crypt unusable to a certain
> degree
> for fs encryption (or at least the initial creation of the fs). Am I
> missing something here or doing something terribly stupid?
Not clear. Certainly haven't had any reports of memory leaks with
dm-crypt. Something must explain the execessive nature of your leak but
it isn't a known issue.
Have you tried running with kmemleak enabled?
--
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>
WARNING: multiple messages have this Message-ID (diff)
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:18:19 -0400 [thread overview]
Message-ID: <20160711131818.GA28102@redhat.com> (raw)
In-Reply-To: <e7af885e08e1ced4f75313bfdfda166d@mail.ud19.udmedia.de>
On Mon, Jul 11 2016 at 4:31am -0400,
Matthias Dahl <ml_linux-kernel@binary-island.eu> wrote:
> Hello,
>
> I made a few more tests and here my observations:
>
> - kernels 4.4.8 and 4.5.5 show the same behavior
>
> - the moment dd starts, memory usage spikes rapidly and within a just
> a few seconds has filled up all 32 GiB of RAM
>
> - dd w/ direct i/o works just fine
>
> - mkfs.ext4 unfortunately shows the same behavior as dd w/o direct i/o
> and such makes creation of an ext4 fs on dm-crypt a game of luck
>
> (much more exposed so with e2fsprogs 1.43.1)
>
> I am kind of puzzled that this bug has seemingly gone so long unnoticed
> since it is rather severe and makes dm-crypt unusable to a certain
> degree
> for fs encryption (or at least the initial creation of the fs). Am I
> missing something here or doing something terribly stupid?
Not clear. Certainly haven't had any reports of memory leaks with
dm-crypt. Something must explain the execessive nature of your leak but
it isn't a known issue.
Have you tried running with kmemleak enabled?
next prev parent reply other threads:[~2016-07-11 13:18 UTC|newest]
Thread overview: 17+ 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 8:31 ` Matthias Dahl
2016-07-11 13:18 ` Mike Snitzer [this message]
2016-07-11 13:18 ` Mike Snitzer
2016-07-11 13:27 ` [dm-devel] " Matthias Dahl
2016-07-11 13:27 ` Matthias Dahl
2016-07-11 13:44 ` Mike Snitzer
2016-07-11 13:44 ` Mike Snitzer
2016-07-11 13:30 ` Mike Snitzer
2016-07-11 13:30 ` Mike Snitzer
2016-07-11 14:47 ` [dm-devel] " Matthias Dahl
2016-07-11 14:47 ` Matthias Dahl
2016-07-12 8:06 ` Matthias Dahl
2016-07-12 8:06 ` Matthias Dahl
-- strict thread matches above, loose matches on Subject: below --
2016-07-10 7:04 Matthias Dahl
2016-07-10 9:23 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=20160711131818.GA28102@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.