Subject: [folded-merged] fs-convert-fs-shrinkers-to-new-scan-count-api-fix-fix.patch removed from -mm tree To: dan.carpenter@xxxxxxxxxx,dchinner@xxxxxxxxxx,glommer@xxxxxxxxxx,mm-commits@xxxxxxxxxxxxxxx From: akpm@xxxxxxxxxxxxxxxxxxxx Date: Tue, 10 Sep 2013 15:31:24 -0700 The patch titled Subject: UBIFS: signedness bug in ubifs_shrink_count() has been removed from the -mm tree. Its filename was fs-convert-fs-shrinkers-to-new-scan-count-api-fix-fix.patch This patch was dropped because it was folded into fs-convert-fs-shrinkers-to-new-scan-count-api.patch ------------------------------------------------------ From: Dan Carpenter <dan.carpenter@xxxxxxxxxx> Subject: UBIFS: signedness bug in ubifs_shrink_count() We test "clean_zn_cnt" for negative later in the function. Signed-off-by: Dan Carpenter <dan.carpenter@xxxxxxxxxx> Cc: Dave Chinner <dchinner@xxxxxxxxxx> Cc: Glauber Costa <glommer@xxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- fs/ubifs/shrinker.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN fs/ubifs/shrinker.c~fs-convert-fs-shrinkers-to-new-scan-count-api-fix-fix fs/ubifs/shrinker.c --- a/fs/ubifs/shrinker.c~fs-convert-fs-shrinkers-to-new-scan-count-api-fix-fix +++ a/fs/ubifs/shrinker.c @@ -280,7 +280,7 @@ static int kick_a_thread(void) unsigned long ubifs_shrink_count(struct shrinker *shrink, struct shrink_control *sc) { - unsigned long clean_zn_cnt = atomic_long_read(&ubifs_clean_zn_cnt); + long clean_zn_cnt = atomic_long_read(&ubifs_clean_zn_cnt); /* * Due to the way UBIFS updates the clean znode counter it may _ Patches currently in -mm which might be from dan.carpenter@xxxxxxxxxx are origin.patch ocfs2-use-list_for_each_entry-instead-of-list_for_each.patch mbind-add-bug_onvma-in-new_vma_page.patch affs-use-loff_t-in-affs_truncate.patch pktcdvd-convert-printk-to-pr_level.patch pktcdvd-fix-defective-misuses-of-pkt_level.patch fs-convert-fs-shrinkers-to-new-scan-count-api.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html