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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 29 Jul 2009 08:59:22 -0700
From:	Frank Mayhar <fmayhar@...gle.com>
To:	Jan Kara <jack@...e.cz>
Cc:	Eric Sandeen <sandeen@...hat.com>,
	Andreas Dilger <adilger@....com>,
	Curt Wohlgemuth <curtw@...gle.com>,
	ext4 development <linux-ext4@...r.kernel.org>
Subject: Re: Question on fallocate/ftruncate sequence (and flags)

On Wed, 2009-07-29 at 17:29 +0200, Jan Kara wrote:
> > On Thu, 2009-07-23 at 15:37 -0500, Eric Sandeen wrote:
> > > As for:
> > > 
> > > #define EXT4_EXT_MIGRATE                0x00100000 /* Inode is migrating */
> > > 
> > > this is not in the mask that FS_IOC_GETFLAGS can see ... and I don't
> > > think anyone else uses FS_DIRECTIO_FL.
> > > 
> > > I'm not sure if the flags not in FS_FL_USER_VISIBLE are supposed to be
> > > fs-unique.
> > 
> > The flag will need to be generic in any case, since inode_setattr() has
> > to look at it when it's deciding whether or not to call vmtruncate().
> > Other filesystems that properly implement fallocate() may want to use it
> > for this purpose as well.
>   Actually, Nick Piggin is changing the truncate path (the patches may
> already be in Al Viro's tree) so that filesystem can come in earlier in
> the truncate path and can make the decision when to truncate and when
> not on its own. I guess this would help you...

Yes, immensely, but it looks like that's a bit in the future...
-- 
Frank Mayhar <fmayhar@...gle.com>
Google, Inc.

--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ