lisa/android_kernel_xiaomi_sm8350
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Kernel Tree For Xiaomi 11 Lite NE 5G
143 Commits 1 Branch 0 Tags 1.8 GiB
C 98%
Assembly 1.2%
Makefile 0.3%
Shell 0.2%
Python 0.1%
c509458c27
Go to file
Sungjong Seo c509458c27 exfat: use updated exfat_chain directly during renaming 
In order for a file to access its own directory entry set,
exfat_inode_info(ei) has two copied values. One is ei->dir, which is
a snapshot of exfat_chain of the parent directory, and the other is
ei->entry, which is the offset of the start of the directory entry set
in the parent directory.

Since the parent directory can be updated after the snapshot point,
it should be used only for accessing one's own directory entry set.

However, as of now, during renaming, it could try to traverse or to
allocate clusters via snapshot values, it does not make sense.

This potential problem has been revealed when exfat_update_parent_info()
was removed by commit d8dad2588add ("exfat: fix referencing wrong parent
directory information after renaming"). However, I don't think it's good
idea to bring exfat_update_parent_info() back.

Instead, let's use the updated exfat_chain of parent directory diectly.

Signed-off-by: Sungjong Seo <sj1557.seo@samsung.com>
Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>
2022-06-08 07:10:06 +09:00
.travis_cmd_wrapper.pl exfat: add travis-CI build and test support 2020-02-03 22:43:47 +09:00
.travis_get_mainline_kernel exfat: add travis-CI build and test support 2020-02-03 22:43:47 +09:00
balloc.c exfat: further fix 'fatal_signal_pending' undeclared 2022-05-18 13:43:00 +09:00
cache.c exfat: fix use of uninitialized spinlock on error path 2020-10-12 22:56:52 +09:00
dir.c exfat: remove argument 'sector' from exfat_get_dentry() 2021-12-16 21:30:53 +09:00
exfat_fs.h exfat: release 5.19.1 version 2022-06-03 23:29:07 +09:00
exfat_raw.h exfat: fix shift-out-of-bounds in exfat_fill_super() 2021-02-01 10:35:05 +09:00
fatent.c exfat: directly call filemap_write_and_wait_range() on < 5.19 kernel 2022-05-19 22:43:01 +09:00
file.c exfat: file: fix build with kernel < 4.4.72 2022-05-16 21:45:05 +09:00
inode.c exfat: fs: Convert __set_page_dirty_buffers to block_dirty_folio 2022-05-11 15:45:27 +09:00
Kconfig exfat: initial commit 2020-02-03 21:47:19 +09:00
Makefile exfat: fix typo in Makefile 2021-10-14 22:24:23 -07:00
misc.c exfat: fix write failure on kernels prior to 4.8. 2022-05-14 08:27:13 +09:00
namei.c exfat: use updated exfat_chain directly during renaming 2022-06-08 07:10:06 +09:00
nls.c exfat: remove argument 'sector' from exfat_get_dentry() 2021-12-16 21:30:53 +09:00
README.md exfat: fix typo 2020-02-10 21:35:58 +09:00
super.c exfat: fix write failure on kernels prior to 4.8. 2022-05-14 08:27:13 +09:00

README.md

exFAT filesystem

This is the exfat filesystem for support from the linux 4.1 kernel to the latest kernel.

Installing as a stand-alone module

Install prerequisite package for Fedora, RHEL:

	yum install kernel-devel-$(uname -r)

Build step:

	make
	sudo make install

To load the driver manually, run this as root:

	modprobe exfat

Installing as a part of the kernel

  1. Let's take [linux] as the path to your kernel source dir.
	cd [linux]
	cp -ar exfat [linux]/fs/
  1. edit [linux]/fs/Kconfig
	source "fs/fat/Kconfig"
	+source "fs/exfat/Kconfig"
	source "fs/ntfs/Kconfig"
  1. edit [linux]/fs/Makefile
	obj-$(CONFIG_FAT_FS)          += fat/
	+obj-$(CONFIG_EXFAT_FS)       += exfat/
	obj-$(CONFIG_BFS_FS)          += bfs/
  1. make menuconfig and set exfat
	File systems  --->
		DOS/FAT/NT Filesystems  --->
			<M> exFAT filesystem support
			(utf8) Default iocharset for exFAT

build your kernel