diff options
author | Theodore Ts'o <tytso@mit.edu> | 2018-12-19 12:29:13 -0500 |
---|---|---|
committer | Theodore Ts'o <tytso@mit.edu> | 2018-12-19 12:29:13 -0500 |
commit | 8a363970d1dc38c4ec4ad575c862f776f468d057 (patch) | |
tree | 4c2f7788f568c974552b1b1a158a0423dbe84f04 /arch/m68k/Makefile | |
parent | a805622a757b6d7f65def4141d29317d8e37b8a1 (diff) | |
download | linux-stable-8a363970d1dc38c4ec4ad575c862f776f468d057.tar.gz linux-stable-8a363970d1dc38c4ec4ad575c862f776f468d057.tar.bz2 linux-stable-8a363970d1dc38c4ec4ad575c862f776f468d057.zip |
ext4: avoid declaring fs inconsistent due to invalid file handles
If we receive a file handle, either from NFS or open_by_handle_at(2),
and it points at an inode which has not been initialized, and the file
system has metadata checksums enabled, we shouldn't try to get the
inode, discover the checksum is invalid, and then declare the file
system as being inconsistent.
This can be reproduced by creating a test file system via "mke2fs -t
ext4 -O metadata_csum /tmp/foo.img 8M", mounting it, cd'ing into that
directory, and then running the following program.
#define _GNU_SOURCE
#include <fcntl.h>
struct handle {
struct file_handle fh;
unsigned char fid[MAX_HANDLE_SZ];
};
int main(int argc, char **argv)
{
struct handle h = {{8, 1 }, { 12, }};
open_by_handle_at(AT_FDCWD, &h.fh, O_RDONLY);
return 0;
}
Google-Bug-Id: 120690101
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Cc: stable@kernel.org
Diffstat (limited to 'arch/m68k/Makefile')
0 files changed, 0 insertions, 0 deletions