From: Theodore Tso <tytso-3s7WtUTddSA@public.gmane.org>
To: jim owens <jowens-VXdhtT5mjnY@public.gmane.org>
Cc: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
Jamie Lokier <jamie-yetKDKU6eevNLxjTenLetw@public.gmane.org>,
linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Mark Fasheh <mfasheh-IBi9RG/b67k@public.gmane.org>,
Michael Kerrisk
<mtk.manpages-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>,
linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/4] vfs: vfs-level fiemap interface
Date: Tue, 7 Oct 2008 14:52:19 -0400 [thread overview]
Message-ID: <20081007185219.GD15929@mit.edu> (raw)
In-Reply-To: <48EB87DE.4090607-VXdhtT5mjnY@public.gmane.org>
Right, thanks. This time in proper English. :-)
* FIEMAP_EXTENT_ENCODED
This extent does not consist of plain filesystem blocks but is
encoded (e.g. encrypted or compressed). Reading the data in this
extent via I/O to the block device will have undefined results.
Note that it is *always* undefined to try to update the data
in-place by writing to the indicated location without the
assistance of the filesystem, or to access the data using the
information returned by the FIEMAP interface while the filesystem
is mounted. In other words, user applications may only read the
extent data via I/O to the block device while the filesystem is
unmounted, and then only if the FIEMAP_EXTENT_ENCODED flag is
clear; user applications must not try reading or writing to the
filesystem via the block device under any other circumstances.
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-api" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next parent reply other threads:[~2008-10-07 18:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081004021251.GA29174@mit.edu>
[not found] ` <48EA55AC.2060102@hp.com>
[not found] ` <20081006210706.GB8139@mit.edu>
[not found] ` <20081007101207.GA10406@infradead.org>
[not found] ` <20081007130008.GA3503@shareable.org>
[not found] ` <20081007130218.GA4316@infradead.org>
[not found] ` <20081007132436.GC3503@shareable.org>
[not found] ` <20081007132854.GA15953@infradead.org>
[not found] ` <20081007154523.GA15929@mit.edu>
[not found] ` <48EB87DE.4090607@hp.com>
[not found] ` <48EB87DE.4090607-VXdhtT5mjnY@public.gmane.org>
2008-10-07 18:52 ` Theodore Tso [this message]
[not found] ` <20081007185219.GD15929-3s7WtUTddSA@public.gmane.org>
2008-10-07 20:31 ` [PATCH 1/4] vfs: vfs-level fiemap interface Christoph Hellwig
[not found] <1223516913-17612-1-git-send-email-tytso@mit.edu>
[not found] ` <1223516913-17612-1-git-send-email-tytso-3s7WtUTddSA@public.gmane.org>
2008-10-09 1:48 ` Theodore Ts'o
[not found] <1223341581-13802-1-git-send-email-tytso@mit.edu>
[not found] ` <1223341581-13802-2-git-send-email-tytso@mit.edu>
[not found] ` <1223341581-13802-2-git-send-email-tytso-3s7WtUTddSA@public.gmane.org>
2008-10-07 1:09 ` Theodore Tso
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=20081007185219.GD15929@mit.edu \
--to=tytso-3s7wtutddsa@public.gmane.org \
--cc=hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=jamie-yetKDKU6eevNLxjTenLetw@public.gmane.org \
--cc=jowens-VXdhtT5mjnY@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mfasheh-IBi9RG/b67k@public.gmane.org \
--cc=mtk.manpages-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.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).