On 2019/3/9 11:58, Luis Chamberlain wrote:
> I so excited about the report, thanks this is awesome work!! However it
> seemed possibly like a paper-over a different issue. I'm not convinced yet.
>
> If prefer a bit more investigation until we can be 100% sure. At this point
> my position would b
+cc Al Viro
On 2019/3/4 21:54, Yue Haibing wrote:
> From: YueHaibing
>
> Syzkaller report this:
>
> kasan: GPF could be caused by NULL-ptr deref or user memory access
> general protection fault: [#1] SMP KASAN PTI
> CPU: 1 PID: 5373 Comm: syz-executor.0 Not tainted 5.0.0-rc8+ #3
> Hardware
ping.
On 2019/3/4 21:54, Yue Haibing wrote:
> From: YueHaibing
>
> Syzkaller report this:
>
> kasan: GPF could be caused by NULL-ptr deref or user memory access
> general protection fault: [#1] SMP KASAN PTI
> CPU: 1 PID: 5373 Comm: syz-executor.0 Not tainted 5.0.0-rc8+ #3
> Hardware name:
From: YueHaibing
Syzkaller report this:
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: [#1] SMP KASAN PTI
CPU: 1 PID: 5373 Comm: syz-executor.0 Not tainted 5.0.0-rc8+ #3
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1
