Prev: check name_len before down_read xattr_sem and sb_read in ext2_xattr_get
Next: [PATCH|RFC] deadline: don't allow aliased requests to starve others
From: Wang Sheng-Hui on 13 Jul 2010 11:10 Hi, The comment for ext2_xattr_get is confusing for it has no parameter named "buffer". I checked the code and think the description is suitable for the parameter "value". Following patch is against 2.6.35-rc5. Please check it. Signed-off-by: Wang Sheng-Hui <crosslonelyover(a)gmail.com> --- fs/ext2/xattr.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/fs/ext2/xattr.c b/fs/ext2/xattr.c index 5ecbbd8..f56b599 100644 --- a/fs/ext2/xattr.c +++ b/fs/ext2/xattr.c @@ -355,7 +355,7 @@ static void ext2_xattr_update_super_block(struct super_block *sb) /* * ext2_xattr_set() * - * Create, replace or remove an extended attribute for this inode. Buffer + * Create, replace or remove an extended attribute for this inode. Value * is NULL to remove an existing extended attribute, and non-NULL to * either replace an existing extended attribute, or create a new extended * attribute. The flags XATTR_REPLACE and XATTR_CREATE -- 1.7.1.1 -- Thanks and Regards, shenghui -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |