All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: Nick Piggin <npiggin@suse.de>
Cc: Dmitry Monakhov <dmonakhov@openvz.org>,
	Al Viro <viro@ZenIV.linux.org.uk>,
	linux-fsdevel@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
	Jan Kara <jack@suse.cz>
Subject: Re: [PATCH 1/2] truncate: introduce new sequence
Date: Wed, 17 Mar 2010 11:04:33 +0200	[thread overview]
Message-ID: <4BA09B21.4040306@panasas.com> (raw)
In-Reply-To: <20100317063547.GF2869@laptop>

On 03/17/2010 08:35 AM, Nick Piggin wrote:
> On Tue, Mar 16, 2010 at 05:01:49PM +0300, Dmitry Monakhov wrote:
>> What is the patch's destiny, was it accepted to some dev-tree?
>> If no, please clarify when it will be accepted.
>> Basically want to move newsize_ok check out from vmtruncate
>> to inode_change_ok to fix nasty bugs in setattr() and it is depends
>> on Nick's patch.
> 
> I guess Al hasn't had a chance to look at them yet. I don't think they
> should change much, though. If you want to base patches on top of it,
> that should be fine. I could submit to -mm in the meantime if you like?
> Let me know also if you want the new-truncate filesystem conversions
> (many of them are done).
> 

I will please need the latest one you have for ext2. (Is there a public
tree with all these?). Could you CC: me on the ext2 patch so I can monitor
it's progress, that would be grate.

> Thanks,
> Nick
> 

Thanks
Boaz

      reply	other threads:[~2010-03-17  9:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-02 11:04 [PATCH 1/2] truncate: introduce new sequence Nick Piggin
2010-03-02 11:07 ` [PATCH 2/2] fs: convert simple fs to new truncate Nick Piggin
2010-03-16 14:01 ` [PATCH 1/2] truncate: introduce new sequence Dmitry Monakhov
2010-03-17  6:35   ` Nick Piggin
2010-03-17  9:04     ` Boaz Harrosh [this message]

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=4BA09B21.4040306@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=dmonakhov@openvz.org \
    --cc=hch@lst.de \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=npiggin@suse.de \
    --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.