linux-kernel - Re: [PATCH 2/2] ARM: delete "*Image is ready" log

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] [day] [month] [year] [list]

Message-ID: <CAK7LNAS-ihNAv0Z2izM6uLqmGsK5yvE1zfXT9bkN3U7DB6v63g@mail.gmail.com>
Date:	Fri, 1 Apr 2016 11:55:09 +0900
From:	Masahiro Yamada <yamada.masahiro@...ionext.com>
To:	Russell King - ARM Linux <linux@....linux.org.uk>
Cc:	Michal Marek <mmarek@...e.cz>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 2/2] ARM: delete "*Image is ready" log

Hi Russell,

2016-04-01 1:53 GMT+09:00 Russell King - ARM Linux <linux@....linux.org.uk>:
> On Fri, Apr 01, 2016 at 01:43:02AM +0900, Masahiro Yamada wrote:
>> Commit 3939f3345050 ("ARM: 8418/1: add boot image dependencies to not
>> generate invalid images") fixed bad image generation in case of
>> parallel building, but as a side effect, Kbuild now descends into
>> arch/arm/boot/ again and again, duplicating the same log messages.
>> This is clumsy.
>>
>> In the example below (incremental build),
>>   "Kernel: arch/arm/boot/Image is ready" is displayed three times.
>>   "Kernel: arch/arm/boot/zImage is ready" is displayed twice.
>
> I disagree.  Image and zImage are the final targets that users are
> interested in, we should tell people that they've been successfully
> created.

Do you mean the Kbuild standard log style like follows is insufficient?

  OBJCOPY arch/arm/boot/Image
  OBJCOPY arch/arm/boot/zImage
  UIMAGE  arch/arm/boot/uImage


-- 
Best Regards
Masahiro Yamada