pkg/report: don't use access size for KASAN reports

Including access size potentially leads to failure to deduplicate
reports when size comes from user or for racy bugs (bug is detected
on different accesses depending on timings).
We already drop size from UAF and OOB, drop it for other bug types.
This commit is contained in:
Dmitry Vyukov 2017-10-17 15:09:01 +02:00
parent a1bdb604cc
commit 6a06c36fe1
2 changed files with 8 additions and 2 deletions

View File

@ -36,7 +36,7 @@ var oopses = []*oops{
},
{
compile("BUG: KASAN: ([a-z\\-]+) on address(?:.*\\n)+?.*(Read|Write) of size ([0-9]+)"),
"KASAN: %[1]v %[2]v of size %[3]v",
"KASAN: %[1]v %[2]v",
},
{
compile("BUG: KASAN: (.*)"),

View File

@ -121,7 +121,13 @@ Write of size 4 by task a.out/6260
[23818.438140] Read of size 4 by task syz-executor/22534
[23818.443211] CPU: 3 PID: 22534 Comm: syz-executor Tainted: G U 3.18.0 #78
`: `KASAN: null-ptr-deref Read of size 4`,
`: `KASAN: null-ptr-deref Read`,
`
==================================================================
BUG: KASAN: wild-memory-access on address ffe7087450a17000
Read of size 205 by task syz-executor1/9018
`: `KASAN: wild-memory-access Read`,
`
[ 149.188010] BUG: unable to handle kernel NULL pointer dereference at 000000000000058c