mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-11-08 11:45:53 -05:00
| Filename | Latest commit message | Latest commit date |
|---|---|---|
9f6c133393
There are a few places in the Minix FS code where the "inode" field of a minix_dir_entry is used without checking first to see if the dirent is really a minix3_dir_entry. The inode number in a V1/V2 dirent is 16 bits, whereas that in a V3 dirent is 32 bits. Accessing it as a 16 bit field when it really should be accessed as a 32 bit field probably kinda sorta works on a little-endian machine, but leads to some rather odd behaviour on big-endian machines. [[email protected]: coding-style fixes] Signed-off-by: Doug Graham <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Linus Torvalds <[email protected]> |
||
| .. | ||
| bitmap.c | ||
| dir.c | ||
| file.c | ||
| inode.c | ||
| itree_common.c | ||
| itree_v1.c | ||
| itree_v2.c | ||
| Kconfig | ||
| Makefile | ||
| minix.h | ||
| namei.c | ||