All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Nick Piggin <npiggin@suse.de>
Cc: Christoph Hellwig <hch@infradead.org>,
	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/4] fs: new truncate sequence
Date: Wed, 8 Jul 2009 06:47:01 -0400	[thread overview]
Message-ID: <20090708104701.GA31419@infradead.org> (raw)
In-Reply-To: <20090708063225.GL2714@wotan.suse.de>

On Wed, Jul 08, 2009 at 08:32:25AM +0200, Nick Piggin wrote:
> Thanks for the patch, I think I will fold it in to the series. I
> think we probably do need to call simple_setsize in inode_setattr
> though (unless you propose to eventually convert every filesystem
> to define a .setattr). This would also require eg. your ext2
> conversion to strip ATTR_SIZE before passing through to inode_setattr.

Yes, we should eventually make .setattr mandatory.  Doing a default
action when a method lacks tends to cause more issues than it solves.

I'm happy to help in doing that part of the conversion (and also other
bits)

> >  int ext2_setattr(struct dentry *dentry, struct iattr *iattr)
> >  {
> >  	struct inode *inode = dentry->d_inode;
> >  	int error;
> >  
> > +	if (iattr->ia_valid & ATTR_SIZE) {
> > +		error = ext2_setsize(inode, iattr->ia_size);
> > +		if (error)
> > +			return error;
> > +	}
> > +
> >  	error = inode_change_ok(inode, iattr);
> >  	if (error)
> >  		return error;
> 
> Probably want to call inode_change_ok first here.

Right now I tried to no reorder anything versus the previous patch.

But yes, we should do all the checks first.  Possibly we can even add
a call to inode_newsize_ok to inode_change_ok, but I'd like to defer
that until all conversions are done and we can easily audit it.

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Nick Piggin <npiggin@suse.de>
Cc: Christoph Hellwig <hch@infradead.org>,
	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/4] fs: new truncate sequence
Date: Wed, 8 Jul 2009 06:47:01 -0400	[thread overview]
Message-ID: <20090708104701.GA31419@infradead.org> (raw)
In-Reply-To: <20090708063225.GL2714@wotan.suse.de>

On Wed, Jul 08, 2009 at 08:32:25AM +0200, Nick Piggin wrote:
> Thanks for the patch, I think I will fold it in to the series. I
> think we probably do need to call simple_setsize in inode_setattr
> though (unless you propose to eventually convert every filesystem
> to define a .setattr). This would also require eg. your ext2
> conversion to strip ATTR_SIZE before passing through to inode_setattr.

Yes, we should eventually make .setattr mandatory.  Doing a default
action when a method lacks tends to cause more issues than it solves.

I'm happy to help in doing that part of the conversion (and also other
bits)

> >  int ext2_setattr(struct dentry *dentry, struct iattr *iattr)
> >  {
> >  	struct inode *inode = dentry->d_inode;
> >  	int error;
> >  
> > +	if (iattr->ia_valid & ATTR_SIZE) {
> > +		error = ext2_setsize(inode, iattr->ia_size);
> > +		if (error)
> > +			return error;
> > +	}
> > +
> >  	error = inode_change_ok(inode, iattr);
> >  	if (error)
> >  		return error;
> 
> Probably want to call inode_change_ok first here.

Right now I tried to no reorder anything versus the previous patch.

But yes, we should do all the checks first.  Possibly we can even add
a call to inode_newsize_ok to inode_change_ok, but I'd like to defer
that until all conversions are done and we can easily audit it.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2009-07-08 10:47 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-07 14:44 [rfc][patch 1/4] fs: new truncate helpers Nick Piggin
2009-07-07 14:44 ` Nick Piggin
2009-07-07 14:46 ` [rfc][patch 2/4] fs: use " Nick Piggin
2009-07-07 14:46   ` Nick Piggin
2009-07-07 14:53   ` Christoph Hellwig
2009-07-07 14:53     ` Christoph Hellwig
2009-07-07 14:48 ` [rfc][patch 3/4] fs: new truncate sequence Nick Piggin
2009-07-07 14:48   ` Nick Piggin
2009-07-07 14:58   ` Christoph Hellwig
2009-07-07 14:58     ` Christoph Hellwig
2009-07-07 15:02     ` Nick Piggin
2009-07-07 15:02       ` Nick Piggin
2009-07-07 15:07       ` Christoph Hellwig
2009-07-07 15:07         ` Christoph Hellwig
2009-07-07 15:48         ` Nick Piggin
2009-07-07 15:48           ` Nick Piggin
2009-07-07 16:30           ` Christoph Hellwig
2009-07-07 16:30             ` Christoph Hellwig
2009-07-08  6:32             ` Nick Piggin
2009-07-08  6:32               ` Nick Piggin
2009-07-08 10:47               ` Christoph Hellwig [this message]
2009-07-08 10:47                 ` Christoph Hellwig
2009-07-08 12:34                 ` Nick Piggin
2009-07-08 12:34                   ` Nick Piggin
2009-07-08 12:40                   ` Christoph Hellwig
2009-07-08 12:40                     ` Christoph Hellwig
2009-07-08 12:48                     ` Nick Piggin
2009-07-08 12:48                       ` Nick Piggin
2009-07-08 16:07                   ` Boaz Harrosh
2009-07-08 16:07                     ` Boaz Harrosh
2009-07-09  7:51                     ` Nick Piggin
2009-07-09  7:51                       ` Nick Piggin
2009-07-12  8:55                       ` Boaz Harrosh
2009-07-12  8:55                         ` Boaz Harrosh
2009-07-12 14:47                         ` Christoph Hellwig
2009-07-12 14:47                           ` Christoph Hellwig
2009-07-12 15:00                           ` Boaz Harrosh
2009-07-12 15:00                             ` Boaz Harrosh
2009-07-13  6:59                           ` Nick Piggin
2009-07-13  6:59                             ` Nick Piggin
2009-07-13  8:54                             ` Boaz Harrosh
2009-07-13  8:54                               ` Boaz Harrosh
2009-07-13  9:00                               ` Nick Piggin
2009-07-13  9:00                                 ` Nick Piggin
2009-07-13 11:17                                 ` Boaz Harrosh
2009-07-13 11:17                                   ` Boaz Harrosh
2009-07-13 11:32                                   ` Nick Piggin
2009-07-13 11:32                                     ` Nick Piggin
2009-07-13 13:53                             ` Christoph Hellwig
2009-07-13 13:53                               ` Christoph Hellwig
2009-07-13 14:05                               ` Nick Piggin
2009-07-13 14:05                                 ` Nick Piggin
2009-07-13 14:10                                 ` Christoph Hellwig
2009-07-13 14:10                                   ` Christoph Hellwig
2009-07-07 14:48 ` [rfc][patch 1/4] fs: new truncate helpers Christoph Hellwig
2009-07-07 14:48   ` Christoph Hellwig
2009-07-07 14:49 ` [rfc][patch 4/4] fs: tmpfs, ext2 use new truncate Nick Piggin
2009-07-07 14:49   ` Nick Piggin
2009-07-07 16:38   ` Christoph Hellwig
2009-07-07 16:38     ` Christoph Hellwig
2009-07-08  6:53     ` Nick Piggin
2009-07-08  6:53       ` Nick Piggin
2009-07-08 11:14       ` Jan Kara
2009-07-08 11:14         ` Jan Kara
2009-07-08 12:22         ` Nick Piggin
2009-07-08 12:22           ` Nick Piggin
2009-07-08 12:32           ` Christoph Hellwig
2009-07-08 12:32             ` Christoph Hellwig
2009-07-08 12:39             ` Nick Piggin
2009-07-08 12:39               ` Nick Piggin
2009-07-08 13:49               ` Christoph Hellwig
2009-07-08 13:49                 ` Christoph Hellwig

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=20090708104701.GA31419@infradead.org \
    --to=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=npiggin@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.