Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+4\/6\]\s+xfs\:\s+use\s+memdup_user\(\)\s*$/: 5 ]

Total 5 documents matching your query.

1. [PATCH 4/6] xfs: use memdup_user() (score: 1)
Author: Li Zefan <lizf@xxxxxxxxxxxxxx>
Date: Wed, 08 Apr 2009 15:08:04 +0800
Remove open-coded memdup_user() Signed-off-by: Li Zefan <lizf@xxxxxxxxxxxxxx> -- fs/xfs/linux-2.6/xfs_ioctl.c | 23 +++++++-- fs/xfs/linux-2.6/xfs_ioctl32.c | 12 ++++-- 2 files changed, 11 insertions(
/archives/xfs/2009-04/msg00040.html (9,602 bytes)

2. Re: [PATCH 4/6] xfs: use memdup_user() (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Wed, 8 Apr 2009 09:22:54 -0400
wouldn't NULL be a better error return for this kind of interface, matching kmalloc? Otherwise the patch looks good to me. Reviewed-by: Christoph Hellwig <hch@xxxxxx>
/archives/xfs/2009-04/msg00042.html (8,723 bytes)

3. Re: [PATCH 4/6] xfs: use memdup_user() (score: 1)
Author: Roland Dreier <rdreier@xxxxxxxxx>
Date: Wed, 08 Apr 2009 10:31:25 -0700
I guess returning an error code from memdup_user() lets callers distinguish between ENOMEM and EFAULT. Not sure if that's important or not but there probably are at least some sites that care. - R.
/archives/xfs/2009-04/msg00044.html (9,297 bytes)

4. Re: [PATCH 4/6] xfs: use memdup_user() (score: 1)
Author: Felix Blyakher <felixb@xxxxxxx>
Date: Wed, 8 Apr 2009 15:06:40 -0500
Signed-off-by: Li Zefan <lizf@xxxxxxxxxxxxxx> -- fs/xfs/linux-2.6/xfs_ioctl.c | 23 +++++++-- fs/xfs/linux-2.6/xfs_ioctl32.c | 12 ++++-- 2 files changed, 11 insertions(+), 24 deletions(-) diff --git a
/archives/xfs/2009-04/msg00046.html (9,146 bytes)

5. Re: [PATCH 4/6] xfs: use memdup_user() (score: 1)
Author: Li Zefan <lizf@xxxxxxxxxxxxxx>
Date: Thu, 09 Apr 2009 08:43:33 +0800
Right, and this API is simlilar to strndup_user().
/archives/xfs/2009-04/msg00047.html (8,337 bytes)


This search system is powered by Namazu