Re: [PATCH] mm: mmap: Fix general protection fault in unlink_file_vma()

2020-10-08 Thread linmiaohe
Andrew Morton wrote: > On Thu, 8 Oct 2020 07:17:18 + linmiaohe wrote: > >> Andrew Morton wrote: >> > On Wed, 16 Sep 2020 05:07:33 -0400 Miaohe Lin wrote: >> > >> >> The syzbot reported the below general protection fault: >> >> > >> >is this using the correct file? I think it is, but please

Re: [PATCH] mm: mmap: Fix general protection fault in unlink_file_vma()

2020-10-08 Thread Andrew Morton
On Thu, 8 Oct 2020 07:17:18 + linmiaohe wrote: > Andrew Morton wrote: > > On Wed, 16 Sep 2020 05:07:33 -0400 Miaohe Lin wrote: > > > >> The syzbot reported the below general protection fault: > >> > >> general protection fault, probably for non-canonical address > >> 0xe00eeaee003b: 00

Re: [PATCH] mm: mmap: Fix general protection fault in unlink_file_vma()

2020-10-08 Thread linmiaohe
Andrew Morton wrote: > On Wed, 16 Sep 2020 05:07:33 -0400 Miaohe Lin wrote: > >> The syzbot reported the below general protection fault: >> >> general protection fault, probably for non-canonical address >> 0xe00eeaee003b: [#1] PREEMPT SMP KASAN >> KASAN: maybe wild-memory-access in ran

Re: [PATCH] mm: mmap: Fix general protection fault in unlink_file_vma()

2020-10-07 Thread Andrew Morton
On Wed, 16 Sep 2020 05:07:33 -0400 Miaohe Lin wrote: > The syzbot reported the below general protection fault: > > general protection fault, probably for non-canonical address > 0xe00eeaee003b: [#1] PREEMPT SMP KASAN > KASAN: maybe wild-memory-access in range > [0x007001d8-0x007

Re: [PATCH] mm: mmap: Fix general protection fault in unlink_file_vma()

2020-10-06 Thread linmiaohe
Friendly ping. > The syzbot reported the below general protection fault: > > general protection fault, probably for non-canonical address > 0xe00eeaee003b: [#1] PREEMPT SMP KASAN > KASAN: maybe wild-memory-access in range > [0x007001d8-0x007001df] > CPU: 1 PID: 10488 Comm:

[PATCH] mm: mmap: Fix general protection fault in unlink_file_vma()

2020-09-16 Thread Miaohe Lin
The syzbot reported the below general protection fault: general protection fault, probably for non-canonical address 0xe00eeaee003b: [#1] PREEMPT SMP KASAN KASAN: maybe wild-memory-access in range [0x007001d8-0x007001df] CPU: 1 PID: 10488 Comm: syz-executor721 Not tainted

Re: general protection fault in unlink_file_vma

2020-09-16 Thread linmiaohe
e/linux vma_merge_fix >console output: https://syzkaller.appspot.com/x/log.txt?x=162e6cc590 >kernel config: https://syzkaller.appspot.com/x/.config?x=3c5f6ce8d5b68299 >dashboard link: https://syzkaller.appspot.com/bug?extid=c5d5a51dcbb558ca0cb5 >compiler: gcc (GCC) 10.1.0-syz

Re: general protection fault in unlink_file_vma

2020-09-16 Thread syzbot
Hello, syzbot has tested the proposed patch but the reproducer is still triggering an issue: kernel BUG at arch/x86/mm/physaddr.c:LINE! [ cut here ] kernel BUG at arch/x86/mm/physaddr.c:28! invalid opcode: [#1] PREEMPT SMP KASAN CPU: 0 PID: 6975 Comm: syz-executor.2

Re: general protection fault in unlink_file_vma

2020-09-15 Thread linmiaohe
> >Hello, > >syzbot has tested the proposed patch but the reproducer is still triggering an >issue: >kernel panic: Fatal exception > >RBP: 0001 R08: R09: >R10: 7ffd30630720 R11: R12: 0118d940 >R13: 0118d940 R14: fff

Re: general protection fault in unlink_file_vma

2020-09-15 Thread syzbot
Hello, syzbot has tested the proposed patch but the reproducer is still triggering an issue: kernel panic: Fatal exception RBP: 0001 R08: R09: R10: 7ffd30630720 R11: R12: 0118d940 R13: 0118d940 R14: ff

Re: general protection fault in unlink_file_vma

2020-09-15 Thread linmiaohe
> Hello, > > syzbot has tested the proposed patch but the reproducer is still triggering > an issue: > kernel panic: corrupted stack end in sys_nanosleep > > Kernel panic - not syncing: corrupted stack end detected inside scheduler > CPU: 0 PID: 13791 Comm: syz-executor.4 Not tainted 5.9.0-rc5-syz

Re: general protection fault in unlink_file_vma

2020-09-15 Thread linmiaohe
syzbot wrote: > Hello, > >syzbot has tested the proposed patch but the reproducer is still triggering an >issue: >kernel panic: corrupted stack end in sys_nanosleep > >Kernel panic - not syncing: corrupted stack end detected inside scheduler >CPU: 0 PID: 13791 Comm: syz-executor.4 Not tainted 5.9

Re: general protection fault in unlink_file_vma

2020-09-15 Thread syzbot
Hello, syzbot has tested the proposed patch but the reproducer is still triggering an issue: kernel panic: corrupted stack end in sys_nanosleep Kernel panic - not syncing: corrupted stack end detected inside scheduler CPU: 0 PID: 13791 Comm: syz-executor.4 Not tainted 5.9.0-rc5-syzkaller #0 Hard

Re: general protection fault in unlink_file_vma

2020-09-13 Thread linmiaohe
Tue, 08 Sep 2020 17:19:17 -0700 > syzbot found the following issue on: > > HEAD commit:59126901 Merge tag 'perf-tools-fixes-for-v5.9-2020-09-03' .. > git tree: upstream > console output: > https://syzkaller.appspot.com/x/log.txt?x=1166cb5d90 > kernel config: > https://syzkaller.ap

Re: general protection fault in unlink_file_vma

2020-09-13 Thread linmiaohe
Hillf Danton wrote: > On Sun, 13 Sep 2020 09:17:26 + linmiaohe wrote: >> >> I reviewed the code carefully these days and I found vma_merge() do only >> fput() the vm_file of the linked vma in remove_next cases. >> This gpf is much likely because the ->mmap() callback can change >> vma->vm_f

Re: general protection fault in unlink_file_vma

2020-09-13 Thread linmiaohe
Hi: Hillf Danton wrote: > Tue, 08 Sep 2020 17:19:17 -0700 >> syzbot found the following issue on: >> general protection fault, probably for non-canonical address >> 0xe00eeaee003b: [#1] PREEMPT SMP KASAN >> KASAN: maybe wild-memory-access in range >> [0x007001d8-0x007001

Re: general protection fault in unlink_file_vma

2020-09-09 Thread linmiaohe
Hillf Danton wrote: >> On Thu, 10 Sep 2020 07:43:41 +0530 Souptick Joarder wrote: >> On Wed, Sep 9, 2020 at 9:45 AM Hillf Danton wrote: >> > Tue, 08 Sep 2020 17:19:17 -0700 >> > > syzbot found the following issue on: >> > > >> > > HEAD commit:59126901 Merge tag >> > > 'perf-tools-fixes-for-v5.

Re: general protection fault in unlink_file_vma

2020-09-09 Thread Souptick Joarder
Hi Hiff, On Wed, Sep 9, 2020 at 9:45 AM Hillf Danton wrote: > > > Tue, 08 Sep 2020 17:19:17 -0700 > > syzbot found the following issue on: > > > > HEAD commit:59126901 Merge tag 'perf-tools-fixes-for-v5.9-2020-09-03' .. > > git tree: upstream > > console output: https://syzkaller.appspo

general protection fault in unlink_file_vma

2020-09-08 Thread syzbot
Hello, syzbot found the following issue on: HEAD commit:59126901 Merge tag 'perf-tools-fixes-for-v5.9-2020-09-03' .. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=1166cb5d90 kernel config: https://syzkaller.appspot.com/x/.config?x=3c5f6ce8d5b68299 das