From: Theodore Tso <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] down i_data_sem only for read when walking tree for fiemap
Date: Sun, 17 May 2009 23:37:03 -0400 [thread overview]
Message-ID: <20090518033703.GG32019@mit.edu> (raw)
In-Reply-To: <4A0DD994.1090200@redhat.com>
On Fri, May 15, 2009 at 04:07:32PM -0500, Eric Sandeen wrote:
> Not sure why I put this in as down_write originally; all we are
> doing is walking the tree, nothing will change under us and
> concurrent reads should be no problem.
Applied, thanks.
- Ted
prev parent reply other threads:[~2009-05-18 3:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 21:07 [PATCH] down i_data_sem only for read when walking tree for fiemap Eric Sandeen
2009-05-18 3:37 ` Theodore Tso [this message]
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=20090518033703.GG32019@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@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).