linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-fsdevel@vger.kernel.org, Jan Kara <jack@suse.cz>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-mm@kvack.org
Subject: Re: [rfc][patch 3/3] fs: convert ext2,tmpfs to new truncate
Date: Mon, 6 Jul 2009 19:59:43 +0200	[thread overview]
Message-ID: <20090706175943.GV2714@wotan.suse.de> (raw)
In-Reply-To: <20090706172838.GC26042@infradead.org>

On Mon, Jul 06, 2009 at 01:28:38PM -0400, Christoph Hellwig wrote:
> On Mon, Jul 06, 2009 at 06:56:29PM +0200, Nick Piggin wrote:
> > 
> > Convert filemap_xip.c, buffer.c, and some filesystems to the new truncate
> > convention. Converting generic helpers is using some ugly code (testing
> > for i_op->ftruncate) to distinguish new and old callers... better
> > alternative might be just define a new function for these guys.
> 
> Splitting generic preparations, ext2 and shmem into separate patch would
> be a tad cleaner I think.

Yes it would.

 
> The testing for the new op is pretty ugly, but this should be just a
> transition help, so it's fine to me.

OK good.

> 
> >  		struct page **pagep, void **fsdata)
> >  {
> > +	int ret;
> > +
> >  	*pagep = NULL;
> > -	return __ext2_write_begin(file, mapping, pos, len, flags, pagep,fsdata);
> > +	ret = __ext2_write_begin(file, mapping, pos, len, flags, pagep,fsdata);
> > +	if (ret < 0) {
> > +		loff_t isize = inode->i_size;
> > +		if (pos + len > isize)
> > +			ext2_ftruncate(NULL, 0, inode, isize);
> > +	}
> > +	return ret;
> > +}
> > +
> > +static int ext2_write_end(struct file *file, struct address_space *mapping,
> > +			loff_t pos, unsigned len, unsigned copied,
> > +			struct page *page, void *fsdata)
> > +{
> > +	int ret;
> > +
> > +	ret = generic_write_end(file, mapping, pos, len, copied, page, fsdata);
> > +	if (ret < len) {
> > +		loff_t isize = inode->i_size;
> > +		if (pos + len > isize)
> > +			ext2_ftruncate(NULL, 0, inode, isize);
> > +	}
> > +	return ret;
> >  }
> >  
> >  static int
> > @@ -770,13 +793,22 @@ ext2_nobh_write_begin(struct file *file,
> >  		loff_t pos, unsigned len, unsigned flags,
> >  		struct page **pagep, void **fsdata)
> >  {
> > +	int ret;
> > +
> >  	/*
> >  	 * Dir-in-pagecache still uses ext2_write_begin. Would have to rework
> >  	 * directory handling code to pass around offsets rather than struct
> >  	 * pages in order to make this work easily.
> >  	 */
> > -	return nobh_write_begin(file, mapping, pos, len, flags, pagep, fsdata,
> > +	ret = nobh_write_begin(file, mapping, pos, len, flags, pagep, fsdata,
> >  							ext2_get_block);
> > +	if (ret < 0) {
> > +		loff_t isize;
> > +		isize = i_size_read(inode);
> > +		if (pos + len > isize)
> > +			ext2_ftruncate(NULL, 0, inode, isize);
> > +	}
> > +	return ret;
> >  }
> >  
> >  static int ext2_nobh_writepage(struct page *page,
> > @@ -796,9 +828,15 @@ ext2_direct_IO(int rw, struct kiocb *ioc
> >  {
> >  	struct file *file = iocb->ki_filp;
> >  	struct inode *inode = file->f_mapping->host;
> > +	ssize_t ret;
> >  
> > -	return blockdev_direct_IO(rw, iocb, inode, inode->i_sb->s_bdev, iov,
> > +	ret = blockdev_direct_IO(rw, iocb, inode, inode->i_sb->s_bdev, iov,
> >  				offset, nr_segs, ext2_get_block, NULL);
> > +	if (ret < 0 && (rw & WRITE)) {
> > +		loff_t isize = i_size_read(inode);
> > +		ext2_ftruncate(NULL, 0, inode, isize);
> 
> These calls don't actually have i_alloc_mutex anymore, do they?

No that's right. But ext2 already had been calling into vmtruncate
without i_alloc_sem (via vmtruncate in write(2) path for trimming
blocks)... hmm, maybe that was a bug itself, though (OTOH, maybe
it doesn't matter because direct IO should not get to blocks
past i_size).


> >  {
> > -	shmem_truncate_range(inode, inode->i_size, (loff_t)-1);
> > +	loff_t oldsize;
> > +	int error;
> > +
> > +	error = inode_truncate_ok(inode, offset);
> > +	if (error)
> > +		return error;
> > +	oldsize = inode->i_size;
> > +	i_size_write(inode, offset);
> > +	truncate_pagecache(inode, oldsize, offset);
> > +	shmem_truncate_range(inode, offset, (loff_t)-1);
> > +
> > +	return error;
> >  }
> 
> Just make this
> 
> 	error = simple_ftruncate(...);
> 	if (!error)
> 		shmem_truncate_range(inode, offset, -1);
> 	return error;

Yes that's better.

Thanks

  reply	other threads:[~2009-07-06 17:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-06 16:54 [rfc][patch 1/3] fs: new truncate sequence Nick Piggin
2009-07-06 16:55 ` [rfc][patch 2/3] fs: make use of new helper functions Nick Piggin
2009-07-06 17:23   ` Christoph Hellwig
2009-07-06 17:47     ` Nick Piggin
2009-07-06 18:05   ` Miklos Szeredi
2009-07-06 16:56 ` [rfc][patch 3/3] fs: convert ext2,tmpfs to new truncate Nick Piggin
2009-07-06 17:28   ` Christoph Hellwig
2009-07-06 17:59     ` Nick Piggin [this message]
2009-07-07  9:17     ` Nick Piggin
2009-07-07 11:45   ` Boaz Harrosh
2009-07-07 13:30     ` Nick Piggin
2009-07-06 17:22 ` [rfc][patch 1/3] fs: new truncate sequence Christoph Hellwig
2009-07-06 17:47   ` Nick Piggin
2009-07-07  7:29     ` Peter Zijlstra
2009-07-07  8:48       ` Nick Piggin
2009-07-06 18:00 ` Miklos Szeredi
2009-07-06 18:10   ` Nick Piggin
2009-07-07 11:45 ` Boaz Harrosh
2009-08-15 14:51 ` Christoph Hellwig
2009-08-15 15:14   ` Nick Piggin
2009-08-15 15:18     ` Christoph Hellwig
2009-08-15 15:36       ` Nick Piggin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090706175943.GV2714@wotan.suse.de \
    --to=npiggin@suse.de \
    --cc=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).