Thread (9 messages) 9 messages, 4 authors, 2007-05-17

Re: [PATCH 1/5][TAKE3] fallocate() implementation on i86, x86_64 and powerpc

From: Amit K. Arora <hidden>
Date: 2007-05-16 12:31:24
Also in: linux-fsdevel, linux-xfs, lkml

On Tue, May 15, 2007 at 05:42:46PM -0700, Mingming Cao wrote:
On Wed, 2007-05-16 at 01:33 +0530, Amit K. Arora wrote:
quoted
This patch implements sys_fallocate() and adds support on i386, x86_64
and powerpc platforms.
quoted
@@ -1137,6 +1148,8 @@ struct inode_operations {
 	ssize_t (*listxattr) (struct dentry *, char *, size_t);
 	int (*removexattr) (struct dentry *, const char *);
 	void (*truncate_range)(struct inode *, loff_t, loff_t);
+	long (*fallocate)(struct inode *inode, int mode, loff_t offset,
+			  loff_t len);
 };
Does the return value from fallocate inode operation has to be *long*?
It's not consistent with the ext4_fallocate() define in patch 4/5, 
I think ->fallocate() should return a "long", since sys_fallocate() has
to return what ->fallocate() returns and hence their return type should
ideally match.
 
+int ext4_fallocate(struct inode *inode, int mode, loff_t offset, loff_t
len)
I will change the ext4_fallocate() to return a "long" (in patch 4/5)
in the next post.

Agree ?

Thanks!
--
Regards,
Amit Arora
thus cause compile warnings.



Mingming
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help