[PATCH] /dev/mem: Fix wrong error on accessing beyond valid memory addresses.
From: Andrei Warkentin
Date: Wed Nov 09 2011 - 18:31:34 EST
Currently this returns -EFAULT, but it really should be returning 0,
as in - 0 bytes read or written. This is what you would get by
opening a block device, seeking to the end, and trying to read
something. Additionally, make lseek() check the sought-to offset
to pass the valid_phys_addr_range test.
Cc: H. Peter Anvin <hpa@xxxxxxxxx>
Signed-off-by: Andrei Warkentin <andreiw@xxxxxxxxxx>
---
drivers/char/mem.c | 9 +++++++--
1 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/drivers/char/mem.c b/drivers/char/mem.c
index 8fc04b4..02d0b1a 100644
--- a/drivers/char/mem.c
+++ b/drivers/char/mem.c
@@ -98,7 +98,7 @@ static ssize_t read_mem(struct file *file, char __user *buf,
char *ptr;
if (!valid_phys_addr_range(p, count))
- return -EFAULT;
+ return 0;
read = 0;
#ifdef __ARCH_HAS_NO_PAGE_ZERO_MAPPED
/* we don't have page 0 mapped on sparc and m68k.. */
@@ -156,7 +156,7 @@ static ssize_t write_mem(struct file *file, const char __user *buf,
void *ptr;
if (!valid_phys_addr_range(p, count))
- return -EFAULT;
+ return 0;
written = 0;
@@ -710,6 +710,11 @@ static loff_t memory_lseek(struct file *file, loff_t offset, int orig)
case SEEK_CUR:
offset += file->f_pos;
case SEEK_SET:
+ if (!valid_phys_addr_range(offset, 0)) {
+ ret = -EINVAL;
+ break;
+ }
+
/* to avoid userland mistaking f_pos=-9 as -EBADF=-9 */
if ((unsigned long long)offset >= ~0xFFFULL) {
ret = -EOVERFLOW;
--
1.7.4.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/