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  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 Mar 2019 20:56:27 +0100
From:   Arnd Bergmann <>
To:     "Luck, Tony" <>
Cc:     Borislav Petkov <>,
        Mauro Carvalho Chehab <>,
        James Morse <>,
        "Zhuo, Qiuxu" <>,
        "" <>,
        Linux Kernel Mailing List <>
Subject: Re: [PATCH] EDAC, {skx|i10nm}_edac: Fix randconfig build error

On Fri, Mar 22, 2019 at 6:55 PM Luck, Tony <> wrote:
> On Fri, Mar 22, 2019 at 03:00:25PM +0100, Arnd Bergmann wrote:
> > Sorry, this was my mistake, my email was garbled. The patch was
> > correct though: the idea here is not to change the Kconfig symbols
> > but to change the Makefile to do the right thing even when Kconfig
> > is set wrong.
> Well this does seem like a "clever" way out of the randconfig
> problem.  New patch applies and when I set .config to have:
> I don't see any build errors.
> There are lots of "skx_" symbols in
> But I'm not at all sure what happened to the I10NM driver.
> I don't see it mentioned in the output from "make".
> It didn't get built as a module (no ".ko" file for it).
> It doesn't seem to be built in (no ".o" in drivers/edac/built-in.a)
> So I added a #error line to the start of i10nm_edac.c and
> ran "make" again.  Nothing.

Oops, I guess my testing method was also insufficient,
I only checked that the bug was gone, not that it actually

> So, I don't think this is doing what you think it should
> do.  Even if it did, it would seem very confusing to a user
> that asked for "one module, one built-in" in Kconfig, but
> found both built-in.
> Boris: I'm voting for Qiuxu's most recent solution (moving
> all the EDAC_DEBUG bits out of skx_common.c).

Yes, that's probably best then. My patch was likely close to
another correct solution, but I've screwed it up twice now ;-)


Powered by blists - more mailing lists