From: Boaz Harrosh <bharrosh@panasas.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Al Viro <viro@ftp.linux.org.uk>, Christoph Hellwig <hch@lst.de>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH ver4] exofs: New truncate sequence
Date: Thu, 10 Jun 2010 15:40:39 +0300 [thread overview]
Message-ID: <4C10DD47.5070604@panasas.com> (raw)
In-Reply-To: <20100609214631.GA31073@ZenIV.linux.org.uk>
On 06/10/2010 12:46 AM, Al Viro wrote:
> On Wed, Jun 09, 2010 at 04:43:23PM +0300, Boaz Harrosh wrote:
>> On 06/09/2010 03:45 PM, Al Viro wrote:
>>> On Wed, Jun 09, 2010 at 02:13:00PM +0300, Boaz Harrosh wrote:
>>>
>>>> Al hi.
>>>>
>>>> Please take this through your tree. And/or tell me if you need it
>>>> reorder with your ->evict patches.
>>>
>>> Um... Don't we need to free on-disk data blocks when inode gets deleted?
>>
>> No, the OSD device takes care of that when you send it an OSD_REMOVE
>> command.
>
> OK, ver5 applied to for-next, evict_inode rediffed. Should show up on
> git.kernel.org shortly.
Thank you Al.
I'm also publishing a few exofs patches on -next through the osd tree.
I have test merges of:
- Base Linus tree - as of today
+ merge vfs/for-next
+ merge vfs/evict_inode
+ merge osd/linux-next - based on Linus
By visual inspection of vfs/evict_inode and vfs/for-next they should not conflict
I will monitor linux-next carefully to make sure we are clean. If there are problems
I'll base my tree on vfs/for-next, which should be good as long as you don't rebase.
Thanks again
Boaz
next prev parent reply other threads:[~2010-06-10 12:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 22:22 [PATCH 47/58] convert exofs to ->evict_inode() Al Viro
2010-06-09 9:05 ` Boaz Harrosh
2010-06-09 10:02 ` Christoph Hellwig
2010-06-09 11:09 ` Boaz Harrosh
2010-06-09 11:10 ` [PATCH ver4] exofs: New truncate sequence Boaz Harrosh
2010-06-09 11:13 ` Boaz Harrosh
2010-06-09 12:45 ` Al Viro
2010-06-09 13:43 ` Boaz Harrosh
2010-06-09 21:46 ` Al Viro
2010-06-10 12:40 ` Boaz Harrosh [this message]
2010-06-09 13:55 ` Christoph Hellwig
2010-06-09 15:26 ` Boaz Harrosh
2010-06-09 15:23 ` [PATCH ver5] " Boaz Harrosh
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=4C10DD47.5070604@panasas.com \
--to=bharrosh@panasas.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
--cc=viro@ftp.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.