The patch titled
Subject: nilfs2-add-bmap-function-to-seek-a-valid-key-fix
has been removed from the -mm tree. Its filename was
nilfs2-add-bmap-function-to-seek-a-valid-key-fix.patch
This patch was dropped because it was folded into nilfs2-add-bmap-function-to-seek-a-valid-key.patch
------------------------------------------------------
From: Ryusuke Konishi <konishi.ryusuke@xxxxxxxxxxxxx>
Subject: nilfs2-add-bmap-function-to-seek-a-valid-key-fix
I've got a report from Dan Carpenter that this range check causes a
warning:
fs/nilfs2/btree.c:1611 nilfs_btree_seek_key() warn: impossible condition '(start > (~0)) => (0-u64max > u64max)'
A range check was needed there in a wip patch, but we no longer need
it.
Cc: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
fs/nilfs2/btree.c | 3 ---
1 file changed, 3 deletions(-)
diff -puN fs/nilfs2/btree.c~nilfs2-add-bmap-function-to-seek-a-valid-key-fix fs/nilfs2/btree.c
--- a/fs/nilfs2/btree.c~nilfs2-add-bmap-function-to-seek-a-valid-key-fix
+++ a/fs/nilfs2/btree.c
@@ -1608,9 +1608,6 @@ static int nilfs_btree_seek_key(const st
const int minlevel = NILFS_BTREE_LEVEL_NODE_MIN;
int ret;
- if (start > NILFS_BTREE_KEY_MAX)
- return -ENOENT;
-
path = nilfs_btree_alloc_path();
if (!path)
return -ENOMEM;
_
Patches currently in -mm which might be from konishi.ryusuke@xxxxxxxxxxxxx are
nilfs2-do-not-use-async-write-flag-for-segment-summary-buffers.patch
nilfs2-use-set_mask_bits-for-operations-on-buffer-state-bitmap.patch
nilfs2-use-bgl_lock_ptr.patch
nilfs2-unify-type-of-key-arguments-in-bmap-interface.patch
nilfs2-add-bmap-function-to-seek-a-valid-key.patch
nilfs2-add-helper-to-find-existent-block-on-metadata-file.patch
nilfs2-improve-execution-time-of-nilfs_ioctl_get_cpinfo-ioctl.patch
nilfs2-fix-gcc-warning-at-nilfs_checkpoint_is_mounted.patch
nilfs2-put-out-gfp-mask-manipulation-from-nilfs_set_inode_flags.patch
nilfs2-use-inode_set_flags-in-nilfs_set_inode_flags.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
