diff options
| author | Theodore Ts'o <tytso@mit.edu> | 2016-03-26 16:14:34 -0400 |
|---|---|---|
| committer | Mister Oyster <oysterized@gmail.com> | 2017-05-29 03:52:07 +0200 |
| commit | 497e4f5904374c294d60bb1112a08c08d4c9b72b (patch) | |
| tree | 1da7006f7d5d8c5ddc7aaa7a6f5360ca7c1aaa39 /kernel | |
| parent | e8c4fbc1bb00a1710a0d68ed943e30eb1283272c (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.
Upstream commit: c9af28fdd44922a6c10c9f8315718408af98e315
Google-Bug-Id: 27641567
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Change-Id: I55b6ab35c9ad4eb2ca6d06380755395f17525496
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions