linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: Tao Ma <tao.ma@oracle.com>
Cc: ocfs2-devel@oss.oracle.com, joel.becker@oracle.com,
	linux-fsdevel@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] ocfs2: Remove the deprecated inode_setattr.
Date: Wed, 9 Jun 2010 19:38:04 +1000	[thread overview]
Message-ID: <20100609093804.GY26335@laptop> (raw)
In-Reply-To: <4C0F5F01.8010807@oracle.com>

On Wed, Jun 09, 2010 at 05:29:37PM +0800, Tao Ma wrote:
> Hi Nick,
> 	Thanks for the quick response.
> On 06/09/2010 05:16 PM, Nick Piggin wrote:
> >On Wed, Jun 09, 2010 at 04:48:20PM +0800, Tao Ma wrote:
> >>@@ -1052,17 +1052,17 @@ int ocfs2_setattr(struct dentry *dentry, struct iattr *attr)
> >>  	}
> >>
> >>  	/*
> >>-	 * This will intentionally not wind up calling simple_setsize(),
> >>-	 * since all the work for a size change has been done above.
> >>-	 * Otherwise, we could get into problems with truncate as
> >>-	 * ip_alloc_sem is used there to protect against i_size
> >>-	 * changes.
> >>+	 * Since all the work for a size change has been done above,
> >>+	 * we only need to call simple_setsize to update i_size.
> >>  	 */
> >>-	status = inode_setattr(inode, attr);
> >>-	if (status<  0) {
> >>-		mlog_errno(status);
> >>-		goto bail_commit;
> >>+	if (attr->ia_valid&  ATTR_SIZE) {
> >>+		status = simple_setsize(inode, attr->ia_size);
> >>+		if (status<  0) {
> >>+			mlog_errno(status);
> >>+			goto bail_commit;
> >>+		}
> >>  	}
> >>+	generic_setattr(inode, attr);
> >>
> >>  	status = ocfs2_mark_inode_dirty(handle, inode, bh);
> >>  	if (status<  0)
> >
> >simple_setsize of course calls inode_newsize_ok, which may fail. If
> >you're committing your on-disk truncates at this point, you will
> >prefer to hoist that check as early as possible so you cannot fail
> >here.
> >
> We have a inode_newsize_ok check at the top of ocfs2_setattr when we
> do the real work of truncate(it is far above, so the patch can't
> have it. ;) ). So we don't need to worry about that actually.

OK, can you comment that or just open-code the truncate part of
simple_setsize? It should be helpful for example with Christoph's
truncate cleanup work.


  reply	other threads:[~2010-06-09  9:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1276073300-7360-1-git-send-email-tao.ma@oracle.com>
2010-06-09  9:16 ` [PATCH] ocfs2: Remove the deprecated inode_setattr Nick Piggin
2010-06-09  9:29   ` Tao Ma
2010-06-09  9:38     ` Nick Piggin [this message]
2010-06-09 10:12       ` Joel Becker
2010-06-09 10:14         ` Christoph Hellwig
2010-06-09 19:53           ` [Ocfs2-devel] " Joel Becker
2010-06-09 10:01   ` Christoph Hellwig
2010-06-09 13:43     ` Tao Ma
     [not found] ` <20100609100839.GA21239@mail.oracle.com>
2010-06-09 10:43   ` 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=20100609093804.GY26335@laptop \
    --to=npiggin@suse.de \
    --cc=hch@lst.de \
    --cc=joel.becker@oracle.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=ocfs2-devel@oss.oracle.com \
    --cc=tao.ma@oracle.com \
    /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).