From: Ulrich Drepper Date: Tue, 24 Jul 2007 01:43:46 +0000 (-0700) Subject: fallocate syscall interface deficiency X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=0d786d4a2773f06a791e8c3730d049077fb81df6;p=GitHub%2Fmoto-9609%2Fandroid_kernel_motorola_exynos9610.git fallocate syscall interface deficiency The fallocate syscall returns ENOSYS in case the filesystem does not support the operation and expects the userlevel code to fill in. This is good in concept. The problem is that the libc code for old kernels should be able to distinguish the case where the syscall is not at all available vs not functioning for a specific mount point. As is this is not possible and we always have to invoke the syscall even if the kernel doesn't support it. I suggest the following patch. Using EOPNOTSUPP is IMO the right thing to do. Cc: Amit Arora Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds --- diff --git a/fs/open.c b/fs/open.c index a6b054edacba..e27c205364d3 100644 --- a/fs/open.c +++ b/fs/open.c @@ -403,7 +403,7 @@ asmlinkage long sys_fallocate(int fd, int mode, loff_t offset, loff_t len) if (inode->i_op && inode->i_op->fallocate) ret = inode->i_op->fallocate(inode, mode, offset, len); else - ret = -ENOSYS; + ret = -EOPNOTSUPP; out_fput: fput(file);