[PATCH 01/20] compat ABI: use non-compat openat and open_by_handle_at variants

2017-06-19 Thread Yury Norov
The only difference is that non-compat version forces O_LARGEFILE, and it should be the default behaviour for all architectures, as we are going to drop the support of 32-bit userspace off_t. The exception is tile32 that continues with compat version of syscalls. Signed-off-by: Yury Norov

[PATCH 01/20] compat ABI: use non-compat openat and open_by_handle_at variants

2017-06-04 Thread Yury Norov
The only difference is that non-compat version forces O_LARGEFILE, and it should be the default behaviour for all architectures, as we don't support 32-bit off_t. The only exception is tile32, that continues with compat version of syscalls. Signed-off-by: Yury Norov

[PATCH 01/20] compat ABI: use non-compat openat and open_by_handle_at variants

2017-03-01 Thread Yury Norov
The only difference is that non-compat version forces O_LARGEFILE, and it should be the default behaviour for all architectures, as we don't support 32-bit off_t. The only exception is tile32, that continues with compat version of syscalls. Signed-off-by: Yury Norov

[PATCH 01/20] compat ABI: use non-compat openat and open_by_handle_at variants

2017-01-09 Thread Yury Norov
The only difference is that non-compat version forces O_LARGEFILE, and it should be the default behaviour for all architectures, as we don't support 32-bit off_t. The only exception is tile32, that continues with compat version of syscalls. Signed-off-by: Yury Norov