diff options
| author | Theodore Ts'o <tytso@mit.edu> | 2016-09-12 10:24:24 +0300 |
|---|---|---|
| committer | Gerrit - the friendly Code Review server <code-review@localhost> | 2016-09-12 01:05:34 -0700 |
| commit | 4dfa31b4af7e936832f657b18fd9f64eb26ed09d (patch) | |
| tree | c8c70055a0f411ef5a7965867a9e835a402083a2 /tools/perf/scripts/python | |
| parent | 911e592fdc0d6c8f63ea2aec181122a5621d4cee (diff) | |
ext4 crypto: don't let data integrity writebacks fail with ENOMEM
We don't want the writeback triggered from the journal commit (in
data=writeback mode) to cause the journal to abort due to
generic_writepages() returning an ENOMEM error. In addition, if
fsync() fails with ENOMEM, most applications will probably not do the
right thing.
So if we are doing a data integrity sync, and ext4_encrypt() returns
ENOMEM, we will submit any queued I/O to date, and then retry the
allocation using GFP_NOFAIL.
Change-Id: Ib16510f0261275a61c2b6870503e67b4b1189bee
Google-Bug-Id: 27641567
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Git-commit: c9af28fdd44922a6c10c9f8315718408af98e315
Git-repo: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git
Signed-off-by: Andrey Markovytch <andreym@codeaurora.org>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions