Hi Chris I am resending this based on the btrfs-unstable tree. Please apply/reply.
Thanks Nikanth Prevent creation of files larger than RLIMIT_FSIZE using fallocate. Currently using posix_fallocate one can bypass an RLIMIT_FSIZE limit and create a larger file than the limit. Add a check for that. Signed-off-by: Nikanth Karthikesan <[email protected]> Cc: Amit K. Arora <[email protected]> --- diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c index f08427c..7870f4f 100644 --- a/fs/btrfs/inode.c +++ b/fs/btrfs/inode.c @@ -6842,6 +6842,11 @@ static long btrfs_fallocate(struct inode *inode, int mode, btrfs_wait_ordered_range(inode, alloc_start, alloc_end - alloc_start); mutex_lock(&inode->i_mutex); + + ret = inode_newsize_ok(inode, (offset + len)); + if (ret) + goto out; + if (alloc_start > inode->i_size) { ret = btrfs_cont_expand(inode, alloc_start); if (ret) -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
