[folded-merged] fat-add-fitrim-ioctl-for-fat-file-system-fix.patch removed from -mm tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The patch titled
     Subject: fat-add-fitrim-ioctl-for-fat-file-system-fix
has been removed from the -mm tree.  Its filename was
     fat-add-fitrim-ioctl-for-fat-file-system-fix.patch

This patch was dropped because it was folded into fat-add-fitrim-ioctl-for-fat-file-system.patch

------------------------------------------------------
From: Wentao Wang <witallwang@xxxxxxxxx>
Subject: fat-add-fitrim-ioctl-for-fat-file-system-fix

If we keep "trimmed" as an u32, there will be a potential shift wrap.

It would be a problem on a larger than 4GB partition with
FAT32. Though most tools who call this ioctl would ignore this value,
it would be great to fix it.

Link: http://lkml.kernel.org/r/87h8l37hub.fsf@xxxxxxxxxxxxxxxxxx
Signed-off-by: Wentao Wang <witallwang@xxxxxxxxx>
Signed-off-by: OGAWA Hirofumi <hirofumi@xxxxxxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---

 fs/fat/fatent.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

--- a/fs/fat/fatent.c~fat-add-fitrim-ioctl-for-fat-file-system-fix
+++ a/fs/fat/fatent.c
@@ -705,8 +705,8 @@ int fat_trim_fs(struct inode *inode, str
 	struct msdos_sb_info *sbi = MSDOS_SB(sb);
 	const struct fatent_operations *ops = sbi->fatent_ops;
 	struct fat_entry fatent;
-	u64 ent_start, ent_end, minlen;
-	u32 free = 0, trimmed = 0;
+	u64 ent_start, ent_end, minlen, trimmed = 0;
+	u32 free = 0;
 	unsigned long reada_blocks, reada_mask, cur_block = 0;
 	int err = 0;
 
_

Patches currently in -mm which might be from witallwang@xxxxxxxxx are

fat-add-fitrim-ioctl-for-fat-file-system.patch




[Index of Archives]     [Kernel Archive]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]

  Powered by Linux