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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 27 Oct 2014 16:39:08 +0100
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Jason Cooper <jason@...edaemon.net>
Cc:	Grant Likely <grant.likely@...retlab.ca>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Rob Herring <rob.herring@...aro.org>
Subject: Re: [git pull] Devicetree changes for v3.15

On Mon, Sep 29, 2014 at 10:52 AM, Linus Walleij
<linus.walleij@...aro.org> wrote:
> On Fri, Sep 26, 2014 at 4:19 PM, Jason Cooper <jason@...edaemon.net> wrote:
>> On Fri, Sep 26, 2014 at 02:30:53PM +0200, Linus Walleij wrote:
>
>> Exact patch is:
>>
>>   f4d4ffc03efc kbuild: dtbs_install: new make target
>>
>>> After this patch a while back I have observed the following behaviour
>>> of the kernel build:
>>>
>>> make zImage
>>> make zImage
>>> -> incremental build, just relink
>>>
>>> make zImage
>>> make dtbs
>>> make zImage
>>> -> The whole kernel gets rebuilt
>>>
>>> So now if I happen to recompile my device trees, I suddenly want
>>> the entire zImage to be rebuilt to? It's by definition not changes that
>>> affect the kernel build :-(
>>>
>>> I noticed this because my build scripts calls make dtbs && make zImage,
>>> and started to rebuild absolutely everything all the time.
>>>
>>> Do you think this can be fixed? It's quite simple to reproduce...
>>
>> Does the attached fix your problem?
>
> Yes!
> Tested-by: Linus Walleij <linus.walleij@...aro.org>
>
> Please get this upstream marked for stable.

So is there a proper fix for this coming or not?

I am suffering from this problem :-(

Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ