lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 19 Mar 2007 14:54:04 +0530 From: "Amit K. Arora" <aarora@...ux.vnet.ibm.com> To: Heiko Carstens <heiko.carstens@...ibm.com> Cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, linux-ext4@...r.kernel.org, xfs@....sgi.com, Andrew Morton <akpm@...ux-foundation.org>, suparna@...ibm.com, cmm@...ibm.com, alex@...sterfs.com, suzuki@...ibm.com Subject: Re: [RFC][PATCH] sys_fallocate() system call On Fri, Mar 16, 2007 at 04:21:03PM +0100, Heiko Carstens wrote: > On Fri, Mar 16, 2007 at 08:01:01PM +0530, Amit K. Arora wrote: > > First of all, thanks for the overwhelming response! > > > > Based on the suggestions received, I have added a new parameter to the > > sys_fallocate() system call - an interger called "mode", just after the > > "fd". Now the system call looks like this: > > > > asmlinkage long sys_fallocate(int fd, int mode, loff_t offset, loff_t len) > > > > Currently we have two modes FA_ALLOCATE and FA_DEALLOCATE, for > > preallocation and deallocation of preallocated blocks respectively. More > > modes can be added, when required. And these modes can be renamed, since > > I am sure these are no way the best ones ! :) > > > > Attached below is the patch which implements this system call. It has > > been currently implemented and tested on i386, ppc64 and x86_64 > > architectures. I am facing some problems while trying to implement this > > on s390, and thus the delay. While I try to get it right on s390(x), we > > thought of posting this patch, so that we can save some time. Parallely > > we will work on getting the patch work on s390, and probably it will > > come as a separate patch. > > What's the problem you face on s390? If it's just the compat wrapper, you > may look at sys_sync_file_range_wrapper. Or I will send a patch if needed. Hi Heiko, Yes, the problem was adding compat wrapper for this. I will appreciate your help in writing it. Only thing is that we might have to wait till the order of the arguments is decided upon. Thanks! -- Regards, Amit Arora - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists