From: Theodore Ts'o <tytso@mit.edu>
To: Lukas Czerner <lczerner@redhat.com>
Cc: linux-ext4@vger.kernel.org, gnehzuil.liu@gmail.com,
dmonakhov@openvz.org, bergwolf@gmail.com
Subject: Re: [PATCH 1/2 v5] ext4: Prevent race while walking extent tree
Date: Wed, 28 Nov 2012 12:35:18 -0500 [thread overview]
Message-ID: <20121128173518.GA24431@thunk.org> (raw)
In-Reply-To: <1353573389-5388-2-git-send-email-lczerner@redhat.com>
Thanks, applied.
- Ted
next prev parent reply other threads:[~2012-11-28 17:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 8:36 [PATCH 0/2 v5] Fix some fiemap problems Lukas Czerner
2012-11-22 8:36 ` [PATCH 1/2 v5] ext4: Prevent race while walking extent tree Lukas Czerner
2012-11-28 17:35 ` Theodore Ts'o [this message]
2012-11-22 8:36 ` [PATCH 2/2 v5] ext4: simple cleanup in fiemap codepath Lukas Czerner
2012-11-28 17:35 ` Theodore Ts'o
-- strict thread matches above, loose matches on Subject: below --
2012-11-21 22:03 [PATCH 0/2 v5] ext4: Fix some fiemap problems Lukas Czerner
2012-11-21 22:03 ` [PATCH 1/2 v5] ext4: Prevent race while walking extent tree Lukas 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=20121128173518.GA24431@thunk.org \
--to=tytso@mit.edu \
--cc=bergwolf@gmail.com \
--cc=dmonakhov@openvz.org \
--cc=gnehzuil.liu@gmail.com \
--cc=lczerner@redhat.com \
--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).