From: Marco Stornelli <marco.stornelli@gmail.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Al Viro <viro@ZenIV.linux.org.uk>, Mark Fasheh <mfasheh@suse.com>,
Joel Becker <jlbec@evilplan.org>,
ocfs2-devel@oss.oracle.com, linux-kernel@vger.kernel.org,
Linux FS Devel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 06/22] ocfs2: drop vmtruncate
Date: Sun, 14 Oct 2012 12:28:20 +0200 [thread overview]
Message-ID: <507A93C4.8020509@gmail.com> (raw)
In-Reply-To: <20121013161951.GC19899@infradead.org>
Il 13/10/2012 18:19, Christoph Hellwig ha scritto:
>> if ((attr->ia_valid & ATTR_SIZE) &&
>> attr->ia_size != i_size_read(inode)) {
>> - status = vmtruncate(inode, attr->ia_size);
>> + status = inode_newsize_ok(inode, attr->ia_size);
>> if (status) {
>> mlog_errno(status);
>> goto bail_commit;
>> }
>> + truncate_setsize(inode, attr->ia_size);
>
> ocfs2 already calls inode_newsize_ok earlier during ocfs2_setattr,
> and there's an XXX comment just above the vmtruncate call about
> how ocfs2 hacks around this. I suspect you just want a plain
> truncate_setsize here and remove the comment above it, but I'd
> like to have the ocfs2 folks confirm that.
>
>
Yep, I quite agree. truncate_setsize can be moved up into to the
previous "if (size_change && attr->ia_size != i_size_read(inode))" where
the truncate code does its work.
next prev parent reply other threads:[~2012-10-14 10:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-06 8:17 [PATCH 06/22] ocfs2: drop vmtruncate Marco Stornelli
2012-10-13 16:19 ` [Ocfs2-devel] " Christoph Hellwig
2012-10-13 16:19 ` Christoph Hellwig
2012-10-14 10:28 ` Marco Stornelli [this message]
2012-10-14 17:49 ` [Ocfs2-devel] New OOPS from OCFS2 + QUOTA Marek Królikowski
2012-10-15 4:44 ` Jie Liu
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=507A93C4.8020509@gmail.com \
--to=marco.stornelli@gmail.com \
--cc=hch@infradead.org \
--cc=jlbec@evilplan.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=ocfs2-devel@oss.oracle.com \
--cc=viro@ZenIV.linux.org.uk \
/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.