[PATCH 1/2] compat ABI: use non-compat openat and open_by_handle_at variants

2016-11-08 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 1/2] compat ABI: use non-compat openat and open_by_handle_at variants

2016-11-08 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 Acked-by: Arnd Bergmann

[PATCH 1/2] compat ABI: use non-compat openat and open_by_handle_at variants

2015-12-29 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 Acked-by: Arnd Bergmann

[PATCH 1/2] compat ABI: use non-compat openat and open_by_handle_at variants

2015-12-29 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

Re: [PATCH 1/2] compat ABI: use non-compat openat and open_by_handle_at variants

2015-12-28 Thread Chris Metcalf
On 12/28/2015 06:18 AM, Arnd Bergmann wrote: On Saturday 26 December 2015 19:06:39 Yury Norov wrote: >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

Re: [PATCH 1/2] compat ABI: use non-compat openat and open_by_handle_at variants

2015-12-28 Thread Arnd Bergmann
On Saturday 26 December 2015 19:06:39 Yury Norov wrote: > 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

Re: [PATCH 1/2] compat ABI: use non-compat openat and open_by_handle_at variants

2015-12-28 Thread Arnd Bergmann
On Saturday 26 December 2015 19:06:39 Yury Norov wrote: > 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

Re: [PATCH 1/2] compat ABI: use non-compat openat and open_by_handle_at variants

2015-12-28 Thread Chris Metcalf
On 12/28/2015 06:18 AM, Arnd Bergmann wrote: On Saturday 26 December 2015 19:06:39 Yury Norov wrote: >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

[PATCH 1/2] compat ABI: use non-compat openat and open_by_handle_at variants

2015-12-26 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 1/2] compat ABI: use non-compat openat and open_by_handle_at variants

2015-12-26 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