>
>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
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
>
>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
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
> 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
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
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
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
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
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
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.
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
12 matches
Mail list logo