Bug 450566 - FEAT: RHEL5.3 backport fallocate syscall
FEAT: RHEL5.3 backport fallocate syscall
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel (Show other bugs)
All Linux
low Severity low
: rc
: ---
Assigned To: Eric Sandeen
Martin Jenner
Depends On:
Blocks: 561396
  Show dependency treegraph
Reported: 2008-06-09 13:10 EDT by Eric Sandeen
Modified: 2010-08-09 05:03 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 561396 (view as bug list)
Last Closed: 2009-01-20 15:22:28 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Eric Sandeen 2008-06-09 13:10:46 EDT
The upstream fallocate syscall allows efficient space preallocation for
filesystems which support it (today: ext4, xfs, and ocfs2).

To fully support new ext4 features for the tech preview in 5.3, we should
backport this new syscall.

Relevant upstream commits for the OS infrastructure:


We should probably also update glibc to wire posix_fallocate to this interface
as well.

Comment 1 Eric Sandeen 2008-06-13 14:12:21 EDT
There are 2 tricky bits to this w.r.t. KABI

1. it requires a new inode operation, ->fallocate.  This gets tested:

+       if (inode->i_op && inode->i_op->fallocate)
+               ret = inode->i_op->fallocate(inode, mode, offset, len);

so it is not safe to do for out-of-tree filesystems; ->fallocate will point off
into junk.  One thought is to add a superblock s_flags flag, MS_HAS_FALLOC, and
filesystems which do have ->fallocate can set this.  Then we only test for
fallocate in the presence of that flag.  The only risk is if some other out of
tree filesystem stole that flag for some reason, but I that's an
acceptable/small risk.

2. it requires BH_Unwritten support (unwritten = allocated but uninitialized). 
This is a buffer head flag not present in RHEL5, and we capped useable flags
with BH_PrivateStart for individual filesystem use.  It might be reasonably safe
to put BH_Unwritten up at bit 31, and assume (hope?) that no out of tree
filesystem uses so many flags as to use up that slot... it's far from foolproof

Comment 4 Don Zickus 2008-09-15 10:17:45 EDT
in kernel-2.6.18-115.el5
You can download this test kernel from http://people.redhat.com/dzickus/el5
Comment 8 errata-xmlrpc 2009-01-20 15:22:28 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.