From: Mark Lord <lkml@rtr.ca>
To: Linux Kernel <linux-kernel@vger.kernel.org>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] fs/compat_ioctl.c: add missing FS_IOC_FIEMAP support
Date: Sat, 01 Aug 2009 11:17:13 -0400 [thread overview]
Message-ID: <4A745C79.8030503@rtr.ca> (raw)
In-Reply-To: <4A74584D.2010300@rtr.ca>
Mark Lord wrote:
..
> Since FIBMAP itself is b0rked on ext4, this leaves no way for a 32-bit
..
To stave off the inevitable question, FIBMAP doesn't appear to cope well
with allocated/uncommitted blocks. Creating a file with fallocate(),
and then immediately running FIBMAP, will not give any allocation data.
Doing a sync() after the fallocate() allows FIBMAP to work again.
FIEMAP doesn't require the sync().
Cheers
next prev parent reply other threads:[~2009-08-01 15:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-01 14:59 [PATCH] fs/compat_ioctl.c: add missing FS_IOC_FIEMAP support Mark Lord
2009-08-01 15:17 ` Mark Lord [this message]
2009-08-03 17:48 ` Mark Lord
2009-08-03 18:00 ` Arnd Bergmann
2009-08-03 18:00 ` Eric Sandeen
2009-08-03 22:07 ` Mark Lord
2009-08-03 22:21 ` Eric Sandeen
2009-08-03 23:22 ` Andrew Morton
2009-08-04 10:39 ` Arnd Bergmann
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=4A745C79.8030503@rtr.ca \
--to=lkml@rtr.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@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).