read_code(): go through vfs_read() instead of calling the method directly
... and don't skip on sanity checks. It's *not* a hot path, TYVM (a couple of calls per a.out execve(), for pity sake) and headers of random a.out binary are not to be trusted. Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
This commit is contained in:
parent
0165e8100b
commit
ec69557982
1 changed files with 1 additions and 1 deletions
|
@ -810,7 +810,7 @@ EXPORT_SYMBOL(kernel_read);
|
|||
|
||||
ssize_t read_code(struct file *file, unsigned long addr, loff_t pos, size_t len)
|
||||
{
|
||||
ssize_t res = file->f_op->read(file, (void __user *)addr, len, &pos);
|
||||
ssize_t res = vfs_read(file, (void __user *)addr, len, &pos);
|
||||
if (res > 0)
|
||||
flush_icache_range(addr, addr + len);
|
||||
return res;
|
||||
|
|
Loading…
Reference in a new issue