From: Ondrej Kozina <okozina@redhat.com>
To: Matthias Dahl <ml_linux-kernel@binary-island.eu>,
Michal Hocko <mhocko@kernel.org>
Cc: linux-raid@vger.kernel.org, linux-mm@kvack.org,
dm-devel@redhat.com, linux-kernel@vger.kernel.org,
Mike Snitzer <snitzer@redhat.com>
Subject: Re: [dm-devel] Page Allocation Failures/OOM with dm-crypt on software RAID10 (Intel Rapid Storage)
Date: Wed, 13 Jul 2016 18:24:51 +0200 [thread overview]
Message-ID: <2704a8dd-48c5-82b8-890e-72bf5e1ed1e1@redhat.com> (raw)
In-Reply-To: <a6e48e37cce530f286e6669fdfc0b3f8@mail.ud19.udmedia.de>
On 07/13/2016 05:32 PM, Matthias Dahl wrote:
>
> No matter what, I have no clue how to further diagnose this issue. And
> given that I already had unsolvable issues with dm-crypt a couple of
> months ago with my old machine where the system simply hang itself or
> went OOM when the swap was encrypted and just a few kilobytes needed to
> be swapped out, I am not so sure anymore I can trust dm-crypt with a
> full disk encryption to the point where I feel "safe"... as-in, nothing
> bad will happen or the system won't suddenly hang itself due to it. Or
> if a bug is introduced, that it will actually be possible to diagnose it
> and help fix it or that it will even be eventually fixed. Which is
> really
> a pity, since I would really have liked to help solve this. With the
> swap issue, I did git bisects, tests, narrowed it down to kernel
> versions
> when said bug was introduced... but in the end, the bug is still present
> as far as I know. :(
>
One step after another. Mathias, your original report was not forgotten,
it's just not so easy to find the real culprit and fix it without
causing yet another regression. See the
https://marc.info/?l=linux-mm&m=146825178722612&w=2 thread...
Not to mention that on current 4.7-rc7 kernels it behaves yet slightly
differently (yet far from ideally).
Regards O.
--
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-13 16:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 8:27 Page Allocation Failures/OOM with dm-crypt on software RAID10 (Intel Rapid Storage) Matthias Dahl
2016-07-12 9:50 ` Michal Hocko
2016-07-12 11:28 ` Matthias Dahl
2016-07-12 11:49 ` Michal Hocko
2016-07-12 11:59 ` Michal Hocko
2016-07-12 12:42 ` Matthias Dahl
2016-07-12 14:07 ` Michal Hocko
2016-07-12 14:56 ` Matthias Dahl
2016-07-13 11:21 ` Michal Hocko
2016-07-13 12:18 ` Michal Hocko
2016-07-13 13:18 ` Matthias Dahl
2016-07-13 13:47 ` Michal Hocko
2016-07-13 15:32 ` Matthias Dahl
2016-07-13 16:24 ` Ondrej Kozina [this message]
2016-07-13 18:24 ` [dm-devel] " Matthias Dahl
2016-07-14 11:18 ` Tetsuo Handa
2016-07-15 7:11 ` Page Allocation Failures/OOM with dm-crypt on software RAID10 (Intel Rapid Storage) with check/repair/sync Matthias Dahl
2016-07-18 7:24 ` 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=2704a8dd-48c5-82b8-890e-72bf5e1ed1e1@redhat.com \
--to=okozina@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-raid@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=ml_linux-kernel@binary-island.eu \
--cc=snitzer@redhat.com \
/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).