From: tytso@mit.edu
To: Jan Kara <jack@suse.cz>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Updated ext4 quota design document
Date: Tue, 22 Jun 2010 17:52:00 -0400 [thread overview]
Message-ID: <20100622215200.GE6843@thunk.org> (raw)
In-Reply-To: <20100622202927.GA9413@quack.suse.cz>
On Tue, Jun 22, 2010 at 10:29:27PM +0200, Jan Kara wrote:
> With metadata which get journaled it should be quite easy. JBD already
> must know before you go and modify buffer contents - that's why
> journal_get_write_access and friends exist. It also makes sure that your
> data cannot be modified from the moment the buffer enters commit upto the
> moment the commit is finished. So you can use buffer commit hook to compute
> and store block checksum safely.
True, but we're also interested in making sure this feature can be
used in the non-journal case as well....
- Ted
next prev parent reply other threads:[~2010-06-22 21:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 12:29 Updated ext4 quota design document Theodore Ts'o
2010-06-22 14:20 ` Jan Kara
2010-06-22 20:08 ` tytso
2010-06-22 20:29 ` Jan Kara
2010-06-22 21:52 ` tytso [this message]
2010-06-23 12:30 ` Jan Kara
2010-07-02 7:41 ` Dmitry Monakhov
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=20100622215200.GE6843@thunk.org \
--to=tytso@mit.edu \
--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).