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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Tue, 13 Feb 2018 16:48:44 -0800
From:   Randy Dunlap <>
To:     Ingo Molnar <>
Cc:     LKML <>, Linux MM <>,
        Andrew Morton <>,
        Fengguang Wu <>,,,
        linux-s390 <>,, X86 ML <>,
        "" <>,
        linux-wireless <>,,
        John Johansen <>,
        Greg Kroah-Hartman <>
Subject: Re: [PATCH] headers: untangle kmemleak.h from mm.h

On 02/11/2018 11:27 PM, Ingo Molnar wrote:
> * Randy Dunlap <> wrote:
>> From: Randy Dunlap <>
>> Currently <linux/slab.h> #includes <linux/kmemleak.h> for no obvious
>> reason. It looks like it's only a convenience, so remove kmemleak.h
>> from slab.h and add <linux/kmemleak.h> to any users of kmemleak_*
>> that don't already #include it.
>> Also remove <linux/kmemleak.h> from source files that do not use it.
>> This is tested on i386 allmodconfig and x86_64 allmodconfig. It
>> would be good to run it through the 0day bot for other $ARCHes.
>> I have neither the horsepower nor the storage space for the other
>> $ARCHes.
>> [slab.h is the second most used header file after module.h; kernel.h
>> is right there with slab.h. There could be some minor error in the
>> counting due to some #includes having comments after them and I
>> didn't combine all of those.]
>> This is Lingchi patch #1 (death by a thousand cuts, applied to kernel
>> header files).
>> Signed-off-by: Randy Dunlap <>
> Nice find:
> Reviewed-by: Ingo Molnar <>
> I agree that it needs to go through 0-day to find any hidden dependencies we might 
> have grown due to this.


This patch has mostly survived both 0day and ozlabs multi-arch testing with
2 build errors being reported by both of them.  I have posted patches for
those separately. (and are attached here)

"lib/test_firmware: add header file to prevent build errors"

"integrity/security: fix digsig.c build error"

Will you see that these are merged or do you want me to repost them?


View attachment "integrity_security_digsig_add_header.patch" of type "text/x-patch" (872 bytes)

View attachment "lib_test_firmware_add_header_file.patch" of type "text/x-patch" (1025 bytes)

Powered by blists - more mailing lists