diff options
author | Eric Biggers <ebiggers@google.com> | 2019-12-31 12:12:22 -0600 |
---|---|---|
committer | Theodore Ts'o <tytso@mit.edu> | 2020-01-17 16:24:54 -0500 |
commit | 68e45330e341dad2d3a0a3f8ef2ec46a2a0a3bbc (patch) | |
tree | ba5c552026c9a7407ac7bba30f86958731feaf3b /fs/ext4/indirect.c | |
parent | 547c556f4db7c09447ecf5f833ab6aaae0c5ab58 (diff) | |
download | linux-68e45330e341dad2d3a0a3f8ef2ec46a2a0a3bbc.tar.gz linux-68e45330e341dad2d3a0a3f8ef2ec46a2a0a3bbc.tar.bz2 linux-68e45330e341dad2d3a0a3f8ef2ec46a2a0a3bbc.zip |
ext4: fix deadlock allocating bio_post_read_ctx from mempool
Without any form of coordination, any case where multiple allocations
from the same mempool are needed at a time to make forward progress can
deadlock under memory pressure.
This is the case for struct bio_post_read_ctx, as one can be allocated
to decrypt a Merkle tree page during fsverity_verify_bio(), which itself
is running from a post-read callback for a data bio which has its own
struct bio_post_read_ctx.
Fix this by freeing the first bio_post_read_ctx before calling
fsverity_verify_bio(). This works because verity (if enabled) is always
the last post-read step.
This deadlock can be reproduced by trying to read from an encrypted
verity file after reducing NUM_PREALLOC_POST_READ_CTXS to 1 and patching
mempool_alloc() to pretend that pool->alloc() always fails.
Note that since NUM_PREALLOC_POST_READ_CTXS is actually 128, to actually
hit this bug in practice would require reading from lots of encrypted
verity files at the same time. But it's theoretically possible, as N
available objects isn't enough to guarantee forward progress when > N/2
threads each need 2 objects at a time.
Fixes: 22cfe4b48ccb ("ext4: add fs-verity read support")
Signed-off-by: Eric Biggers <ebiggers@google.com>
Link: https://lore.kernel.org/r/20191231181222.47684-1-ebiggers@kernel.org
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Diffstat (limited to 'fs/ext4/indirect.c')
0 files changed, 0 insertions, 0 deletions