lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 12 Dec 2016 07:58:03 +0100 From: Dmitry Vyukov <dvyukov@...gle.com> To: syzkaller <syzkaller@...glegroups.com> Cc: Catalin Marinas <catalin.marinas@....com>, Will Deacon <will.deacon@....com>, Ard Biesheuvel <ard.biesheuvel@...aro.org>, Mark Rutland <mark.rutland@....com>, Rob Herring <robh@...nel.org>, Kefeng Wang <wangkefeng.wang@...wei.com>, AKASHI Takahiro <takahiro.akashi@...aro.org>, Jon Masters <jcm@...hat.com>, David Daney <david.daney@...ium.com>, Ganapatrao Kulkarni <gkulkarni@...iumnetworks.com>, Andrew Morton <akpm@...ux-foundation.org>, Nicolai Stange <nicstange@...il.com>, James Morse <james.morse@....com>, Andrey Ryabinin <aryabinin@...tuozzo.com>, Andrey Konovalov <andreyknvl@...gle.com>, linux-arm-kernel@...ts.infradead.org, LKML <linux-kernel@...r.kernel.org>, Quentin Casasnovas <quentin.casasnovas@...cle.com> Subject: Re: [PATCH 2/2] kcov: make kcov work properly with KASLR enabled On Sun, Dec 11, 2016 at 10:37 PM, Alexander Popov <alex.popov@...ux.com> wrote: > On 11.12.2016 12:32, Dmitry Vyukov wrote: >> On Sun, Dec 11, 2016 at 1:50 AM, Alexander Popov <alex.popov@...ux.com> wrote: >>> Subtract KASLR offset from the kernel addresses reported by kcov. >>> Tested on x86_64 and AArch64 (Hikey LeMaker). >>> >>> Signed-off-by: Alexander Popov <alex.popov@...ux.com> >>> --- >>> kernel/kcov.c | 8 +++++++- >>> 1 file changed, 7 insertions(+), 1 deletion(-) >> >> I think generally this is the right thing to do. >> >> There are 2 pending patches for kcov by +Quentin (hopefully in mm): >> "kcov: add AFL-style tracing" >> "kcov: size of arena is now given in bytes" >> https://groups.google.com/forum/#!topic/syzkaller/gcqbIhKjGcY >> https://groups.google.com/d/msg/syzkaller/gcqbIhKjGcY/KQFryjBKCAAJ >> >> Your patch probably conflicts with them. >> Should you base them on top of these patches, so that Andrew can merge >> it without conflicts? > > Excuse me, I can't find these patches in: > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git > git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git > git://git.cmpxchg.org/linux-mmots.git > > Could you point at the tree which I can rebase onto? > Should I cherry-pick Quentin's patches manually? Quentin, do you know destiny of your patches? They does not seem to be in mm tree.
Powered by blists - more mailing lists