Looking at src changes this is probably expected, Nov 20 snapshot is still
affected.
login: uvm_fault(0x81cbc100, 0x80b6e000, 0, 1) -> e
kernel: page fault trap, code=0
Stopped at uvm_unmap_remove+0x212: movq0x100(%r13),%r8
ddb{7}> set $lines = 0
ddb{7}> show panic
kernel
Hi Mike,
> Known issue. And the parameters in the list aren't right (there needs to
be
> something added to clang/llvm to support reading the params properly).
This is happening often enough to create toil for running syzkaller with
VMM. Is there a workaround that you know of? As things stand I
On Tue, Oct 30, 2018 at 09:17:19PM -0700, Greg Steuck wrote:
> My syzkaller machine running a recent snapshot just crashed. The value
> 0x415efd243b54d319 passed into uvm_map_deallocate looks quite fishy to me.
>
Known issue. And the parameters in the list aren't right (there needs to be
My syzkaller machine running a recent snapshot just crashed. The value
0x415efd243b54d319 passed into uvm_map_deallocate looks quite fishy to me.
Some hopefully useful info below.
ddb{4}> trace
