diff options
| author | Heiko Carstens <heiko.carstens@de.ibm.com> | 2012-08-08 09:32:20 +0200 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2012-08-26 15:12:10 -0700 |
| commit | 44d3398477f343c8d63f7219ef0594fa06644e0a (patch) | |
| tree | a47f4059583275513edb4dd6d843c84271bf97e3 /fs/fuse/file.c | |
| parent | a422ca75bd264cd26bafeb6305655245d2ea7c6b (diff) | |
| download | kernel_samsung_smdk4412-44d3398477f343c8d63f7219ef0594fa06644e0a.zip kernel_samsung_smdk4412-44d3398477f343c8d63f7219ef0594fa06644e0a.tar.gz kernel_samsung_smdk4412-44d3398477f343c8d63f7219ef0594fa06644e0a.tar.bz2 | |
s390/compat: fix mmap compat system calls
commit e85871218513c54f7dfdb6009043cb638f2fecbe upstream.
The native 31 bit and the compat behaviour for the mmap system calls differ:
In native 31 bit mode the passed in address for the mmap system call will be
unmodified passed to sys_mmap_pgoff().
In compat mode however the passed in address will be modified with
compat_ptr() which masks out the most significant bit.
The result is that in native 31 bit mode each mmap request (with MAP_FIXED)
will fail where the most significat bit is set, while in compat mode it
may succeed.
This odd behaviour was introduced with d3815898 "[S390] mmap: add missing
compat_ptr conversion to both mmap compat syscalls".
To restore a consistent behaviour accross native and compat mode this
patch functionally reverts the above mentioned commit.
Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs/fuse/file.c')
0 files changed, 0 insertions, 0 deletions