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
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 22 Dec 2017 10:51:15 +0900
From:   Joonsoo Kim <>
To:     Andrew Morton <>
Cc:     Andrey Ryabinin <>,
        Alexander Potapenko <>,
        Dmitry Vyukov <>,,,,
        Namhyung Kim <>,
        Wengang Wang <>
Subject: Re: [PATCH 00/18] introduce a new tool, valid access checker

On Tue, Nov 28, 2017 at 04:48:35PM +0900, wrote:
> From: Joonsoo Kim <>
> Hello,
> This patchset introduces a new tool, valid access checker.
> Vchecker is a dynamic memory error detector. It provides a new debug feature
> that can find out an un-intended access to valid area. Valid area here means
> the memory which is allocated and allowed to be accessed by memory owner and
> un-intended access means the read/write that is initiated by non-owner.
> Usual problem of this class is memory overwritten.
> Most of debug feature focused on finding out un-intended access to
> in-valid area, for example, out-of-bound access and use-after-free, and,
> there are many good tools for it. But, as far as I know, there is no good tool
> to find out un-intended access to valid area. This kind of problem is really
> hard to solve so this tool would be very useful.
> This tool doesn't automatically catch a problem. Manual runtime configuration
> to specify the target object is required.
> Note that there was a similar attempt for the debugging overwritten problem
> however it requires manual code modifying and recompile.
> To get more information about vchecker, please see a documention at
> the last patch.
> Patchset can also be available at
> Enjoy it.
> Thanks.

Hello, Andrew.

Before the fixing some build failure on this patchset, I'd like to know
other reviewer's opinion on this patchset, especially, yours. :)

There are some interests on this patchset from some developers. Wengang
come up with a very similar change and Andi said that this looks useful.
Do you think that this tool is useful and can be merged?


Powered by blists - more mailing lists