linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: "Lukáš Czerner" <lczerner@redhat.com>
Cc: Zach Brown <zab@redhat.com>, Peng Tao <bergwolf@gmail.com>,
	linux-ext4@vger.kernel.org, dmonakhov@openvz.org
Subject: Re: [PATCH v3] ext4: Prevent race while waling extent tree
Date: Sun, 18 Nov 2012 22:24:30 -0500	[thread overview]
Message-ID: <20121119032430.GB24414@thunk.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1211151714520.27888@dhcp-1-104.brq.redhat.com>

On Thu, Nov 15, 2012 at 05:39:06PM +0100, Lukáš Czerner wrote:
> You're both right. The code have to be reorganized. The
> ext4_ext_fiemap_cb() is ugly as hell, but luckily that will be
> resolved with extent status tree patches from Zheng Liu, however the
> indirection in ext4_ext_walk_space() and the callback business
> is also pointless.

Hi Lukas,

Is your patch going to be dependent on whether the extent status tree
patches are applied?

If so, you might want to develop your patch versus the ext4 git tree's
master branch, which includes the extent status patches currently
queued for the next merge window.

Thanks!!

					- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2012-11-19  3:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-12 14:57 [PATCH] ext4: Prevent race while waling extent tree Lukas Czerner
2012-11-13  8:22 ` [PATCH v3] " Lukas Czerner
2012-11-13 11:34   ` Peng Tao
2012-11-13 12:07     ` Lukáš Czerner
2012-11-13 14:19       ` Peng Tao
2012-11-13 18:51         ` Zach Brown
2012-11-15 16:39           ` Lukáš Czerner
2012-11-15 19:10             ` Zach Brown
2012-11-19  3:24             ` Theodore Ts'o [this message]
2012-11-19 11:11               ` Lukáš Czerner

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=20121119032430.GB24414@thunk.org \
    --to=tytso@mit.edu \
    --cc=bergwolf@gmail.com \
    --cc=dmonakhov@openvz.org \
    --cc=lczerner@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=zab@redhat.com \
    /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).