linux-stable.git/fs/exfat, branch linux-6.2.y

exfat: fix inode->i_blocks for non-512 byte sector size device

2023-03-10T08:29:29+00:00

commit 39c1ce8eafc0ff64fb9e28536ccc7df6a8e2999d upstream.

inode->i_blocks is not real number of blocks, but 512 byte ones.

Fixes: 98d917047e8b ("exfat: add file operations")
Cc: stable@vger.kernel.org # v5.7+
Reported-by: Wang Yugui 
Tested-by: Wang Yugui 
Signed-off-by: Yuezhang Mo 
Reviewed-by: Andy Wu 
Signed-off-by: Namjae Jeon 
Signed-off-by: Greg Kroah-Hartman

exfat: redefine DIR_DELETED as the bad cluster number

2023-03-10T08:29:29+00:00

commit bdaadfd343e3cba49ad0b009ff4b148dad0fa404 upstream.

When a file or a directory is deleted, the hint for the cluster of
its parent directory in its in-memory inode is set as DIR_DELETED.
Therefore, DIR_DELETED must be one of invalid cluster numbers. According
to the exFAT specification, a volume can have at most 2^32-11 clusters.
However, DIR_DELETED is wrongly defined as 0xFFFF0321, which could be
a valid cluster number. To fix it, let's redefine DIR_DELETED as
0xFFFFFFF7, the bad cluster number.

Fixes: 1acf1a564b60 ("exfat: add in-memory and on-disk structures and headers")
Cc: stable@vger.kernel.org # v5.7+
Reported-by: Yuezhang Mo 
Signed-off-by: Sungjong Seo 
Signed-off-by: Namjae Jeon 
Signed-off-by: Greg Kroah-Hartman

exfat: fix unexpected EOF while reading dir

2023-03-10T08:29:29+00:00

commit 6cb5d1a16a51d080fbc1649a5144cbc5ca7d6f88 upstream.

If the position is not aligned with the dentry size, the return
value of readdir() will be NULL and errno is 0, which means the
end of the directory stream is reached.

If the position is aligned with dentry size, but there is no file
or directory at the position, exfat_readdir() will continue to
get dentry from the next dentry. So the dentry gotten by readdir()
may not be at the position.

After this commit, if the position is not aligned with the dentry
size, round the position up to the dentry size and continue to get
the dentry.

Fixes: ca06197382bd ("exfat: add directory operations")
Cc: stable@vger.kernel.org # v5.7+
Reported-by: Wang Yugui 
Signed-off-by: Yuezhang Mo 
Reviewed-by: Andy Wu 
Reviewed-by: Aoyama Wataru 
Reviewed-by: Sungjong Seo 
Signed-off-by: Namjae Jeon 
Signed-off-by: Greg Kroah-Hartman

exfat: fix reporting fs error when reading dir beyond EOF

2023-03-10T08:29:29+00:00

commit 706fdcac002316893434d753be8cfb549fe1d40d upstream.

Since seekdir() does not check whether the position is valid, the
position may exceed the size of the directory. We found that for
a directory with discontinuous clusters, if the position exceeds
the size of the directory and the excess size is greater than or
equal to the cluster size, exfat_readdir() will return -EIO,
causing a file system error and making the file system unavailable.

Reproduce this bug by:

seekdir(dir, dir_size + cluster_size);
dirent = readdir(dir);

The following log will be printed if mount with 'errors=remount-ro'.

[11166.712896] exFAT-fs (sdb1): error, invalid access to FAT (entry 0xffffffff)
[11166.712905] exFAT-fs (sdb1): Filesystem has been set read-only

Fixes: 1e5654de0f51 ("exfat: handle wrong stream entry size in exfat_readdir()")
Cc: stable@vger.kernel.org # v5.7+
Signed-off-by: Yuezhang Mo 
Reviewed-by: Andy Wu 
Reviewed-by: Aoyama Wataru 
Reviewed-by: Sungjong Seo 
Signed-off-by: Namjae Jeon 
Signed-off-by: Greg Kroah-Hartman

Merge tag 'exfat-for-6.2-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/linkinjeon/exfat

2022-12-16T02:14:21+00:00

Pull exfat update from Namjae Jeon:

 - simplify and remove some redundant directory entry code

 - optimize the size of exfat_entry_set_cache and its allocation policy

 - improve the performance for creating files and directories

* tag 'exfat-for-6.2-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/linkinjeon/exfat:
  exfat: reuse exfat_find_location() to simplify exfat_get_dentry_set()
  exfat: fix overflow in sector and cluster conversion
  exfat: remove i_size_write() from __exfat_truncate()
  exfat: remove argument 'size' from exfat_truncate()
  exfat: remove unnecessary arguments from exfat_find_dir_entry()
  exfat: remove unneeded codes from __exfat_rename()
  exfat: remove call ilog2() from exfat_readdir()
  exfat: replace magic numbers with Macros
  exfat: rename exfat_free_dentry_set() to exfat_put_dentry_set()
  exfat: move exfat_entry_set_cache from heap to stack
  exfat: support dynamic allocate bh for exfat_entry_set_cache
  exfat: reduce the size of exfat_entry_set_cache
  exfat: hint the empty entry which at the end of cluster chain
  exfat: simplify empty entry hint

exfat: reuse exfat_find_location() to simplify exfat_get_dentry_set()

2022-12-13T11:17:16+00:00

In exfat_get_dentry_set(), part of the code is the same as
exfat_find_location(), reuse exfat_find_location() to simplify
exfat_get_dentry_set().

Code refinement, no functional changes.

Signed-off-by: Yuezhang Mo 
Reviewed-by: Andy Wu 
Reviewed-by: Aoyama Wataru 
Reviewed-by: Sungjong Seo 
Signed-off-by: Namjae Jeon

exfat: fix overflow in sector and cluster conversion

2022-12-13T11:17:11+00:00

According to the exFAT specification, there are at most 2^32-11
clusters in a volume. so using 'int' is not enough for cluster
index, the return value type of exfat_sector_to_cluster() should
be 'unsigned int'.

Signed-off-by: Yuezhang Mo 
Reviewed-by: Sungjong Seo 
Signed-off-by: Namjae Jeon

extfat: remove ->writepage

2022-12-12T02:12:17+00:00

Patch series "start removing writepage instances v2".

The VM doesn't need or want ->writepage for writeback and is fine with
just having ->writepages as long as ->migrate_folio is implemented.

This series removes all ->writepage instances that use
block_write_full_page directly and also have a plain mpage_writepages
based ->writepages.


This patch (of 7):

->writepage is a very inefficient method to write back data, and only used
through write_cache_pages or a a fallback when no ->migrate_folio method
is present.

Set ->migrate_folio to the generic buffer_head based helper, and remove
the ->writepage implementation.

Link: https://lkml.kernel.org/r/20221202102644.770505-1-hch@lst.de
Link: https://lkml.kernel.org/r/20221202102644.770505-2-hch@lst.de
Signed-off-by: Christoph Hellwig 
Acked-by: Namjae Jeon 
Acked-by: Johannes Weiner 
Cc: Bob Copeland 
Cc: Dave Kleikamp 
Cc: Jan Kara 
Cc: Mikulas Patocka 
Cc: OGAWA Hirofumi 
Cc: Sungjong Seo 
Signed-off-by: Andrew Morton

exfat: remove i_size_write() from __exfat_truncate()

2022-12-12T02:02:51+00:00

The file/directory size is updated into inode by i_size_write()
before __exfat_truncate() is called, so it is redundant to
re-update by i_size_write() in __exfat_truncate().

Code refinement, no functional changes.

Signed-off-by: Yuezhang Mo 
Reviewed-by: Andy Wu 
Reviewed-by: Aoyama Wataru 
Reviewed-by: Sungjong Seo 
Signed-off-by: Namjae Jeon

exfat: remove argument 'size' from exfat_truncate()

2022-12-12T02:02:51+00:00

argument 'size' is not used in exfat_truncate(), remove it.

Code refinement, no functional changes.

Signed-off-by: Yuezhang Mo 
Reviewed-by: Andy Wu 
Reviewed-by: Aoyama Wataru 
Reviewed-by: Sungjong Seo 
Signed-off-by: Namjae Jeon