summaryrefslogtreecommitdiffstats
path: root/drivers/md/raid10.c
diff options
context:
space:
mode:
authorAl Viro <viro@ZenIV.linux.org.uk>2012-12-02 18:55:07 +0100
committerLinus Torvalds <torvalds@linux-foundation.org>2012-12-02 19:46:38 +0100
commit9d73fc2d641f8831c9dc803177fe47c02120cc36 (patch)
tree266020ef9f36f1a9e09cb7c84d5058ff735575c1 /drivers/md/raid10.c
parentMerge branch 'for-3.7-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git... (diff)
downloadlinux-9d73fc2d641f8831c9dc803177fe47c02120cc36.tar.xz
linux-9d73fc2d641f8831c9dc803177fe47c02120cc36.zip
open*(2) compat fixes (s390, arm64)
The usual rules for open()/openat()/open_by_handle_at() are 1) native 32bit - don't force O_LARGEFILE in flags 2) native 64bit - force O_LARGEFILE in flags 3) compat on 64bit host - as for native 32bit 4) native 32bit ABI for 64bit system (mips/n32, x86/x32) - as for native 64bit There are only two exceptions - s390 compat has open() forcing O_LARGEFILE and arm64 compat has open_by_handle_at() doing the same thing. The same binaries on native host (s390/31 and arm resp.) will *not* force O_LARGEFILE, so IMO both are emulation bugs. Objections? The fix is obvious... Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers/md/raid10.c')
0 files changed, 0 insertions, 0 deletions