The patch titled
use use SEEK_MAX to validate user lseek arguments
has been removed from the -mm tree. Its filename was
use-use-seek_max-to-validate-user-lseek-arguments.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
Subject: use use SEEK_MAX to validate user lseek arguments
From: Chris Snook <csnook@xxxxxxxxxx>
Add SEEK_MAX and use it to validate lseek arguments from userspace.
Signed-off-by: Chris Snook <csnook@xxxxxxxxxx>
Acked-by: David Howells <dhowells@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
fs/read_write.c | 4 ++--
include/linux/fs.h | 1 +
2 files changed, 3 insertions(+), 2 deletions(-)
diff -puN fs/read_write.c~use-use-seek_max-to-validate-user-lseek-arguments fs/read_write.c
--- a/fs/read_write.c~use-use-seek_max-to-validate-user-lseek-arguments
+++ a/fs/read_write.c
@@ -139,7 +139,7 @@ asmlinkage off_t sys_lseek(unsigned int
goto bad;
retval = -EINVAL;
- if (origin <= 2) {
+ if (origin <= SEEK_MAX) {
loff_t res = vfs_llseek(file, offset, origin);
retval = res;
if (res != (loff_t)retval)
@@ -166,7 +166,7 @@ asmlinkage long sys_llseek(unsigned int
goto bad;
retval = -EINVAL;
- if (origin > 2)
+ if (origin > SEEK_MAX)
goto out_putf;
offset = vfs_llseek(file, ((loff_t) offset_high << 32) | offset_low,
diff -puN include/linux/fs.h~use-use-seek_max-to-validate-user-lseek-arguments include/linux/fs.h
--- a/include/linux/fs.h~use-use-seek_max-to-validate-user-lseek-arguments
+++ a/include/linux/fs.h
@@ -30,6 +30,7 @@
#define SEEK_SET 0 /* seek relative to beginning of file */
#define SEEK_CUR 1 /* seek relative to current file position */
#define SEEK_END 2 /* seek relative to end of file */
+#define SEEK_MAX SEEK_END
/* And dynamically-tunable limits and defaults: */
struct files_stat_struct {
_
Patches currently in -mm which might be from csnook@xxxxxxxxxx are
origin.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
