ext4 crypto: don't let data integrity writebacks fail with ENOMEM

Browse source

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.

Google-Bug-Id: 27641567

Signed-off-by: Theodore Ts'o <tytso@mit.edu>

...

This commit is contained in:

Theodore Ts'o 2016-03-26 16:14:34 -04:00

parent 9e92f48c34

commit c9af28fdd4

4 changed files with 39 additions and 20 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

37

fs/ext4/crypto.c

View file

6

fs/ext4/ext4.h

View file

14

fs/ext4/page-io.c

View file

2

fs/ext4/readpage.c

View file