Re: [PATCH] fs/sync.c: Fix UBSAN Undefined behaviour in sync_file_range

2019-08-28 Thread David Sterba
On Tue, Aug 27, 2019 at 05:22:37PM +0200, Jan Kara wrote: > On Fri 12-07-19 10:28:37, SunKe wrote: > > There is a UBSAN report: > > UBSAN: Undefined behaviour in ../fs/sync.c:298:10 > > signed integer overflow: > > -8 + -9223372036854775807 cannot be represented in type 'long long int' > > CPU: 0 P

Re: [PATCH] fs/sync.c: Fix UBSAN Undefined behaviour in sync_file_range

2019-08-27 Thread Jan Kara
On Fri 12-07-19 10:28:37, SunKe wrote: > There is a UBSAN report: > UBSAN: Undefined behaviour in ../fs/sync.c:298:10 > signed integer overflow: > -8 + -9223372036854775807 cannot be represented in type 'long long int' > CPU: 0 PID: 15876 Comm: syz-executor.3 Not tainted > Hardware name: QEMU KVM V

[PATCH] fs/sync.c: Fix UBSAN Undefined behaviour in sync_file_range

2019-07-11 Thread SunKe
There is a UBSAN report: UBSAN: Undefined behaviour in ../fs/sync.c:298:10 signed integer overflow: -8 + -9223372036854775807 cannot be represented in type 'long long int' CPU: 0 PID: 15876 Comm: syz-executor.3 Not tainted Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 Call trace: [