From: Davide Italiano <dccitaliano@gmail.com>
To: linux-btrfs@vger.kernel.org
Cc: Davide Italiano <dccitaliano@gmail.com>
Subject: [PATCH] Improve FL_KEEP_SIZE handling
Date: Mon, 6 Apr 2015 22:09:14 -0700 [thread overview]
Message-ID: <1428383355-1686-1-git-send-email-dccitaliano@gmail.com> (raw)
This matches the logic of ext4. I think it's more
correct passing (offset + len) to inode_newsize_ok()
rather than rounding up to block size.
The call can be skipped in some cases too. It works for
me but I'm new to this code so I might miss something.
Let me know what you think.
Davide Italiano (1):
Btrfs: Improve FL_KEEP_SIZE handling in fallocate.
fs/btrfs/file.c | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
--
2.3.4
next reply other threads:[~2015-04-07 5:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 5:09 Davide Italiano [this message]
2015-04-07 5:09 ` [PATCH] Btrfs: Improve FL_KEEP_SIZE handling in fallocate Davide Italiano
2015-04-20 20:49 ` Davide Italiano
2015-06-25 17:55 ` Davide Italiano
2015-06-26 3:35 ` Liu Bo
2015-06-26 14:08 ` David Sterba
2015-07-22 17:45 ` Davide Italiano
2015-10-21 17:16 ` Davide Italiano
2016-03-17 14:29 ` David Sterba
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=1428383355-1686-1-git-send-email-dccitaliano@gmail.com \
--to=dccitaliano@gmail.com \
--cc=linux-btrfs@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).