linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Allison Henderson <achender@linux.vnet.ibm.com>
To: Ext4 Developers List <linux-ext4@vger.kernel.org>
Cc: Jan Kara <jack@suse.cz>
Subject: Ext4 Punch Hole Change Summary v6->v7
Date: Sat, 07 May 2011 16:53:50 -0700	[thread overview]
Message-ID: <4DC5DB8E.7050805@linux.vnet.ibm.com> (raw)

Hi All,

This is an updated copy of punch hole that has the while loop 
optimization for ext4_ext_remove_space (in patch 3/5).  The optimization 
limits the tree searching to only the extents that are to be removed 
instead of searching the entire tree.

Also, I updated my base code to the latest copy of the ext4 code, and 
one of the punch hole test cases found a null pointer bug when trying to 
create a directory when the disk is full.  It is not directly related to 
punch hole, so I put it in a separate patch.  Jan, this looks like it 
may have been related to the "[PATCH 1/2] ext4: Fix fs corruption when 
make_indexed_dir() fails" patch.  Would you mind taking a look at it and 
giving it your OK if everything looks good?  Thx!

Allison Henderson

                 reply	other threads:[~2011-05-07 23:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4DC5DB8E.7050805@linux.vnet.ibm.com \
    --to=achender@linux.vnet.ibm.com \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    /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).