summaryrefslogtreecommitdiff
path: root/mm/vma_init.c
diff options
context:
space:
mode:
authorAl Viro <viro@zeniv.linux.org.uk>2025-12-13 17:50:23 -0500
committerAl Viro <viro@zeniv.linux.org.uk>2025-12-16 00:57:29 -0500
commite1b4c6a58304fd490124cc2b454d80edc786665c (patch)
treeebb2e81a49c5e82413e3c2c09a0f550cf86704c0 /mm/vma_init.c
parent3010f06c52aa7da51493df59303ea733a614597b (diff)
shmem: fix recovery on rename failures
maple_tree insertions can fail if we are seriously short on memory; simple_offset_rename() does not recover well if it runs into that. The same goes for simple_offset_rename_exchange(). Moreover, shmem_whiteout() expects that if it succeeds, the caller will progress to d_move(), i.e. that shmem_rename2() won't fail past the successful call of shmem_whiteout(). Not hard to fix, fortunately - mtree_store() can't fail if the index we are trying to store into is already present in the tree as a singleton. For simple_offset_rename_exchange() that's enough - we just need to be careful about the order of operations. For simple_offset_rename() solution is to preinsert the target into the tree for new_dir; the rest can be done without any potentially failing operations. That preinsertion has to be done in shmem_rename2() rather than in simple_offset_rename() itself - otherwise we'd need to deal with the possibility of failure after successful shmem_whiteout(). Fixes: a2e459555c5f ("shmem: stable directory offsets") Reviewed-by: Christian Brauner <brauner@kernel.org> Reviewed-by: Chuck Lever <chuck.lever@oracle.com> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'mm/vma_init.c')
0 files changed, 0 insertions, 0 deletions