Prev: [103/165] ext4: Code cleanup for EXT4_IOC_MOVE_EXT ioctl
Next: [108/165] ext4: Issue the discard operation *before* releasing the blocks to be reused
From: Greg KH on 30 Jul 2010 13:40
2.6.32-stable review patch. If anyone has any objections, please let us know.

------------------

commit 6d19c42b7cf81c39632b6d4dbc514e8449bcd346 upstream (as of v2.6.34-git13)

Currently using posix_fallocate one can bypass an RLIMIT_FSIZE limit
and create a file larger than the limit. Add a check for that.

Signed-off-by: Nikanth Karthikesan <knikanth(a)suse.de>
Signed-off-by: Amit Arora <aarora(a)in.ibm.com>
Signed-off-by: "Theodore Ts'o" <tytso(a)mit.edu>
Signed-off-by: Greg Kroah-Hartman <gregkh(a)suse.de>
---
fs/ext4/extents.c | 5 +++++
1 file changed, 5 insertions(+)

--- a/fs/ext4/extents.c
+++ b/fs/ext4/extents.c
@@ -3607,6 +3607,11 @@ long ext4_fallocate(struct inode *inode,
*/
credits = ext4_chunk_trans_blocks(inode, max_blocks);
mutex_lock(&inode->i_mutex);
+ ret = inode_newsize_ok(inode, (len + offset));
+ if (ret) {
+ mutex_unlock(&inode->i_mutex);
+ return ret;
+ }
retry:
while (ret >= 0 && ret < max_blocks) {
block = block + ret;


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [103/165] ext4: Code cleanup for EXT4_IOC_MOVE_EXT ioctl
Next: [108/165] ext4: Issue the discard operation *before* releasing the blocks to be reused