All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Theodore Tso <tytso@mit.edu>
Cc: cmm@us.ibm.com, sandeen@redhat.com, linux-ext4@vger.kernel.org,
	Jan Kara <jack@suse.cz>
Subject: Re: [PATCH -V2 2/2] ext4: truncate the file properly if we fail to copy data from userspace
Date: Tue, 9 Jun 2009 01:50:49 +0530	[thread overview]
Message-ID: <20090608202049.GC23723@skywalker> (raw)
In-Reply-To: <20090608191420.GM23883@mit.edu>

On Mon, Jun 08, 2009 at 03:14:20PM -0400, Theodore Tso wrote:
> On Mon, Jun 08, 2009 at 10:13:57PM +0530, Aneesh Kumar K.V wrote:
> > I think i both the case Jan's patch
> > allocate-blocks-correctly-with-subpage-blocksize need an update ? Since you have put
> > the patch before Jan's changes.
> 
> OK, here's how I updated Jan's patch.  I'm going to assume that we'll
> submit the ext4 patch queue immediately as soon as the merge window
> opens, since my impression is Jan is still waiting for some mm
> developers to review his patch set.   
> 
> Annesh, does this look good to you?

I just did a quick look. Should we do a block_unlock_hole_extend after
journal_stop. We do a block_lock_hole_extend before journal_start.

> 
> Jan, if we go down this path, you'll need to update your ext4 patch
> with this updated one, to take into account the changes from Aneesh's
> patch.
> 
> (We could do it the other way, but that means even more patches queued
> up behind Jan's patch series, and I didn't realize originally that
> Aneesh intended for these to be queued after Jan's patches.  So it
> seemed easier to just order Aneesh's patches to avoid block allocation
> leaks first, since they are at least functionally (if not
> syntactically) independent of the subpagesize blocksize patches.)

-aneesh

  parent reply	other threads:[~2009-06-08 20:21 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26 18:21 [PATCH] ext3: Avoid false EIO errors Jan Kara
2009-03-27 18:08 ` Aneesh Kumar K.V
2009-03-27 20:24   ` Jan Kara
2009-03-30  8:25     ` Aneesh Kumar K.V
2009-03-30 10:32       ` Jan Kara
2009-03-30 10:58         ` Aneesh Kumar K.V
2009-03-30 16:05           ` Jan Kara
2009-03-31  4:45             ` Aneesh Kumar K.V
2009-03-31  9:29               ` [PATCH 1/2] [PATCH] ext4: Add inode to the orphan list during block allocation failure Aneesh Kumar K.V
2009-03-31  9:29                 ` [PATCH 2/2] [PATCH] ext4: truncate the file properly if we fail to copy data from userspace Aneesh Kumar K.V
2009-03-31  9:38                   ` Jan Kara
2009-04-05  3:22                   ` Theodore Tso
2009-04-06 10:07                     ` Jan Kara
2009-03-31  9:34                 ` [PATCH 1/2] [PATCH] ext4: Add inode to the orphan list during block allocation failure Jan Kara
2009-04-05  3:11                 ` Theodore Tso
2009-04-06 10:05                   ` Jan Kara
2009-06-05  4:31                     ` Theodore Tso
2009-06-05  6:22                       ` Theodore Tso
2009-06-05  7:24                         ` Theodore Tso
2009-06-05 23:42                           ` Jan Kara
2009-06-05 23:44                       ` Jan Kara
2009-06-08  4:35                         ` [PATCH -V2 1/2] " Aneesh Kumar K.V
2009-06-08  4:35                           ` [PATCH -V2 2/2] ext4: truncate the file properly if we fail to copy data from userspace Aneesh Kumar K.V
2009-06-08 16:29                             ` Theodore Tso
2009-06-08 16:43                               ` Aneesh Kumar K.V
2009-06-08 19:14                                 ` Theodore Tso
2009-06-08 19:23                                   ` Jan Kara
2009-06-08 20:20                                   ` Aneesh Kumar K.V [this message]
2009-06-09 10:12                                     ` Jan Kara
2009-06-08 16:29                           ` [PATCH -V2 1/2] ext4: Add inode to the orphan list during block allocation failure Theodore Tso
2009-03-31  9:46               ` [PATCH] ext3: Avoid false EIO errors (version 4) Jan Kara
2009-04-01  0:06                 ` Andrew Morton
2009-04-01  9:49                   ` Jan Kara
2009-03-30 13:53       ` [PATCH] ext3: Avoid false EIO errors Eric Sandeen
2009-03-30 14:45         ` Aneesh Kumar K.V
2009-03-30 15:12           ` Eric Sandeen

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=20090608202049.GC23723@skywalker \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=cmm@us.ibm.com \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=tytso@mit.edu \
    /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.