From: Joel Becker <Joel.Becker@oracle.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Tao Ma <tao.ma@oracle.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Nick Piggin <npiggin@suse.de>
Subject: Re: [PATCH v4] ocfs2: Let ocfs2_setattr use new truncate sequence.
Date: Fri, 11 Jun 2010 00:50:20 -0700 [thread overview]
Message-ID: <20100611075020.GC23946@mail.oracle.com> (raw)
In-Reply-To: <20100611071945.GA20496@lst.de>
On Fri, Jun 11, 2010 at 09:19:45AM +0200, Christoph Hellwig wrote:
> On Fri, Jun 11, 2010 at 03:16:13PM +0800, Tao Ma wrote:
> > oh, that would be much work for ocfs2 to do from my perspective. So I
> > would really want to leave it as-is and I have add it to my to-do list.
>
> Oh right, you start a new transaction there. Sorry, ignore my request
> and keep it as it is for now. I don't think doing truncatate in separate
> transactions actually is correct, though but that's no change with this
> patch.
Christoph,
You're missing the part where actual truncate (reduce i_size)
sets i_size in ocfs2_truncate_file(). So this later code doesn't get
triggered for the truncate case. It exists for the extend case, where
we extend the allocation in multiple clean transactions, then finally
set i_size in a final transaction.
Joel
--
"When choosing between two evils, I always like to try the one
I've never tried before."
- Mae West
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2010-06-11 7:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 3:27 [PATCH v4] ocfs2: Let ocfs2_setattr use new truncate sequence Tao Ma
2010-06-11 4:50 ` Nick Piggin
2010-06-11 6:56 ` Christoph Hellwig
2010-06-11 7:16 ` Tao Ma
2010-06-11 7:19 ` Christoph Hellwig
2010-06-11 7:50 ` Joel Becker [this message]
2010-06-11 7:55 ` Joel Becker
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=20100611075020.GC23946@mail.oracle.com \
--to=joel.becker@oracle.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
--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 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.