linux-ext4 - [Patch 0/2] Persistent preallocation in ext4 (using fallocate inode op)

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

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070321121951.GB27273@amitarora.in.ibm.com>
Date:	Wed, 21 Mar 2007 17:49:51 +0530
From:	"Amit K. Arora" <aarora@...ux.vnet.ibm.com>
To:	Mingming Cao <cmm@...ibm.com>
Cc:	Dave Kleikamp <shaggy@...ux.vnet.ibm.com>,
	Theodore Tso <tytso@....edu>,
	ext4 development <linux-ext4@...r.kernel.org>
Subject: [Patch 0/2] Persistent preallocation in ext4 (using fallocate inode op)

On Mon, Mar 19, 2007 at 09:15:22AM -0800, Mingming Cao wrote:
> On Mon, 2007-03-19 at 10:48 -0500, Dave Kleikamp wrote:
> > persistent_allocation_1_ioctl_and_unitialized_extents
> 
> We could mention here that this patch is going to be replaced by a new
> patch to use the fallocate() operations.
> 
> > # Fixed an endian error
> > persistent_allocation_2_support_for_writing_to_unitialized_extent
> 
> I think Amit has an updated version of this patch in his place.

Hi Mingming,

Here are the new patches which use new fallocate inode interface. I have
made following changes to the previous patchset:

1. Removed ioctl portion of the code from the preallocation patch.
2. Added ext4_fallocate() to support the new fallocate inode operation,
which will be called from the sys_fallocate() system call code.
3. Fixed the endian error which you observed in the "write support for
uninitialized extents" patch.

--
Regards,
Amit Arora
-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html