linux-kernel - Re: [PATCH] vfs: pass struct file to do_truncate on O

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] [day] [month] [year] [list]

Message-ID: <20100316174719.GA24819@shell>
Date:	Tue, 16 Mar 2010 13:47:19 -0400
From:	Valerie Aurora <vaurora@...hat.com>
To:	Al Viro <viro@...IV.linux.org.uk>
Cc:	Jeff Layton <jlayton@...hat.com>,
	Trond Myklebust <trond.myklebust@....uio.no>,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	linux-nfs@...r.kernel.org
Subject: Re: [PATCH] vfs: pass struct file to do_truncate on O_TRUNC opens

On Mon, Mar 15, 2010 at 10:50:37PM +0000, Al Viro wrote:
> On Mon, Mar 15, 2010 at 06:47:02PM -0400, Jeff Layton wrote:
> 
> > Yeah that would be cleaner on the wire for the create case. It's not
> > clear to me how to implement that though. There doesn't appear to be
> > a straightforward way to tell the VFS to skip the truncate.
> 
> The plan is to turn most of the guts of do_last() into fs method...

For union mounts, we will want to skip the truncate too (or else
insinuate ourselves into do_truncate() - less attractive).  This is
because we want to only copy up the bytes that are not being
truncated, instead of copying up the file contents and then throwing
them away.

What's the timing on the do_last() change?  Do you know what branch it
will be in?

Thanks,

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