From: Nick Piggin <npiggin@suse.de>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: Jan Kara <jack@suse.cz>, Al Viro <viro@ZenIV.linux.org.uk>,
Christoph Hellwig <hch@infradead.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [patch 2/5] fs: convert simple fs to new truncate
Date: Thu, 10 Dec 2009 18:57:07 +1100 [thread overview]
Message-ID: <20091210075706.GA23196@nick> (raw)
In-Reply-To: <4B20B4D8.1050503@panasas.com>
On Thu, Dec 10, 2009 at 10:44:08AM +0200, Boaz Harrosh wrote:
> On 12/10/2009 07:15 AM, Nick Piggin wrote:
> >
> > Al, any chance to merge patches 1 and 2 upstream early in this round? They
> > should be fairly non intrusive and back compatible. Then I can get the
> > filesystem specific patches to their maintainers and you won't have to
> > bother with them.
> >
> > ecryptfs is being fixed to use notify_change rather than vmtruncate (which
> > is anyway buggy today), so that won't be a problem.
> >
> > I think we'll be able to get rid of old protocol completely within just
> > a couple of releases. Jan and Christoph have made pretty good progress
> > there.
> >
>
> Nick Hi.
>
> I want to do the exofs conversion. Is there a public git-tree with all this that
> I can base my work, and run tests?
>
> Thanks
> Boaz
Hi Boaz,
I don't have any git trees published. Apart from merging the patch by
hand, I should hope it goes upstream with Al's vfs merge.
If you've got patches based on the previous patchset in Al's tree,
then it is identical except that we don't switch those helper functions
with the .truncate_kludge = 1 flag but instead use _newtrunc variants.
Thanks,
Nick
next prev parent reply other threads:[~2009-12-10 8:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-08 8:38 [patch 1/5] fs: truncate introduce new sequence Nick Piggin
2009-12-08 8:39 ` [patch 2/5] fs: convert simple fs to new truncate Nick Piggin
2009-12-09 14:39 ` Jan Kara
2009-12-10 5:15 ` Nick Piggin
2009-12-10 8:44 ` Boaz Harrosh
2009-12-10 7:57 ` Nick Piggin [this message]
2009-12-08 8:41 ` [patch 3/5] tmpfs: convert to use the new truncate convention Nick Piggin
2009-12-09 14:45 ` Jan Kara
2009-12-10 0:48 ` Nick Piggin
2009-12-08 8:42 ` [patch 4/5] ext2: " Nick Piggin
2009-12-09 14:57 ` Jan Kara
2009-12-10 1:11 ` Nick Piggin
2009-12-10 10:20 ` Jan Kara
2009-12-08 8:43 ` [patch 5/5] fat: " Nick Piggin
2009-12-09 15:08 ` Jan Kara
2009-12-09 14:38 ` [patch 1/5] fs: truncate introduce new sequence Jan Kara
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=20091210075706.GA23196@nick \
--to=npiggin@suse.de \
--cc=bharrosh@panasas.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--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 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).