From: John Haxby <john.haxby@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 0/1] ocfs2: return non-zero st_blocks for inline data [resend2]
Date: Tue, 24 Nov 2015 21:07:00 +0000 [thread overview]
Message-ID: <1448399221-6109-1-git-send-email-john.haxby@oracle.com> (raw)
Hello All,
[Really sorry about this and I hope you're not getting fed up of
multiple copies of this message but the list on oss.oracle.com really
doesn't like me.]
Some programs, and programmers, assume that if a file is occupying
zero blocks (st_blocks == 0) then it contains no data and there's no
point in reading it. Posix doesn't actually say anything about this,
but it seems to be something a lot of people expect. Indeed, ext4,
btrfs and ntfs-3d all seem to behave this way so that no one[1] has
any unpleasant surprises.
This patch is almost exactly the same as commit 9206c561554c ("ext4:
return non-zero st_blocks for inline data") although I couldn't bring
myself to include the typo in the comment :)
jch
[resend because rejected by list the first time.]
[1] tar, I'm looking at you, but you're not the only one.
John Haxby (1):
ocfs2: return non-zero st_blocks for inline data
fs/ocfs2/file.c | 8 ++++++++
1 file changed, 8 insertions(+)
--
2.5.0
next reply other threads:[~2015-11-24 21:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 21:07 John Haxby [this message]
2015-11-24 21:07 ` [Ocfs2-devel] [PATCH 1/1] ocfs2: return non-zero st_blocks for inline data John Haxby
2015-11-25 2:53 ` Gang He
2015-12-01 7:08 ` Junxiao Bi
2015-12-01 22:33 ` John Haxby
2015-12-02 2:47 ` Junxiao Bi
2015-12-18 22:34 ` Mark Fasheh
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=1448399221-6109-1-git-send-email-john.haxby@oracle.com \
--to=john.haxby@oracle.com \
--cc=ocfs2-devel@oss.oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.