From: Christoph Hellwig <hch@lst.de>
To: Steven Whitehouse <steve@chygwyn.com>
Cc: Christoph Hellwig <hch@lst.de>,
viro@zeniv.linux.org.uk, npiggin@suse.de, jack@suse.cz,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 2/2] check ATTR_SIZE contraints in inode_change_ok
Date: Tue, 1 Jun 2010 13:47:03 +0200 [thread overview]
Message-ID: <20100601114703.GA5169@lst.de> (raw)
In-Reply-To: <1275392975.2346.4.camel@localhost>
On Tue, Jun 01, 2010 at 12:49:35PM +0100, Steven Whitehouse wrote:
> Hi,
>
> Can you drop the GFS2 bit from this? I've got patches for the new
> truncate sequence for GFS2 and that bit you have altered in the patch
> below doesn't exist after that patch is applied,
I'd really prefer to get all these preparation in before converting
filesystems if possible. They change a lot of the helpers to be used
in ->setattr, so getting the infrastructure right should make it
a lot more clear what's happening in the filesystem code.
next prev parent reply other threads:[~2010-06-01 11:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 11:39 [PATCH 0/2] new truncate sequence, part3 Christoph Hellwig
2010-06-01 11:39 ` [PATCH 1/2] always call inode_change_ok early in ->setattr Christoph Hellwig
2010-06-01 11:39 ` [PATCH 2/2] check ATTR_SIZE contraints in inode_change_ok Christoph Hellwig
2010-06-01 11:49 ` Steven Whitehouse
2010-06-01 11:47 ` Christoph Hellwig [this message]
2010-06-09 7:33 ` Nick Piggin
2010-06-09 9:41 ` Jan Kara
2010-06-09 10:06 ` Nick Piggin
2010-06-09 10:07 ` Christoph Hellwig
2010-06-09 10:26 ` Nick Piggin
2010-06-10 8:21 ` Christoph Hellwig
2010-06-09 10:59 ` Steven Whitehouse
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=20100601114703.GA5169@lst.de \
--to=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=steve@chygwyn.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.