ext4: bubble errors from ext4_find_inline_data_nolock() up to ext4_iget()
authorTheodore Ts'o <tytso@mit.edu>
Tue, 22 May 2018 21:14:07 +0000 (17:14 -0400)
committerTheodore Ts'o <tytso@mit.edu>
Tue, 22 May 2018 21:14:07 +0000 (17:14 -0400)
commiteb9b5f01c33adebc31cbc236c02695f605b0e417
tree22cc5a91463b52193fdf1c6dc0465a33c767fd78
parent117166efb1ee8f13c38f9e96b258f16d4923f888
ext4: bubble errors from ext4_find_inline_data_nolock() up to ext4_iget()

If ext4_find_inline_data_nolock() returns an error it needs to get
reflected up to ext4_iget().  In order to fix this,
ext4_iget_extra_inode() needs to return an error (and not return
void).

This is related to "ext4: do not allow external inodes for inline
data" (which fixes CVE-2018-11412) in that in the errors=continue
case, it would be useful to for userspace to receive an error
indicating that file system is corrupted.

Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Reviewed-by: Andreas Dilger <adilger@dilger.ca>
Cc: stable@kernel.org
fs/ext4/inode.c