[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+r1ZhjvZmDjuoroL-N6s1SU6+CQwBM0izjvP9kigGO7ThW5kQ@mail.gmail.com>
Date: Fri, 28 Oct 2016 15:32:32 -0700
From: Jim Davis <jim.epost@...il.com>
To: SF Markus Elfring <elfring@...rs.sourceforge.net>
Cc: linux-kbuild@...r.kernel.org, Michal Marek <mmarek@...e.com>,
LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org
Subject: Re: [PATCH 01/10] scripts/basic/bin2c: Complete error handling in main()
On Fri, Oct 28, 2016 at 1:31 AM, SF Markus Elfring
<elfring@...rs.sourceforge.net> wrote:
> From: Markus Elfring <elfring@...rs.sourceforge.net>
> Date: Thu, 27 Oct 2016 16:15:04 +0200
>
> Return values were not checked from five calls of the function "printf".
>
> This issue was detected also by using the Coccinelle software.
>
>
> * Add a bit of exception handling there.
>
> * Optimise this function implementation a bit.
The most interesting thing about this patch was trying to figure out
how to actually get bin2c to run at all. Making a defconfig kernel
didn't run it. Making a kernel with the latest Ubuntu 16.10 config
file didn't run it. Setting CONFIG_IKCONFIG runs it (once), for the
folks who want to use scripts/extract-ikconfig. After that, if you
dig about in the makefiles, it looks like you have to turn on the
Tomoyo LSM -- which doesn't seem to be a common occurrence -- or else
set CONFIG_KEXEC_FILE to generate the 'purgatory' thing it uses.
Again, not the most frequent of events, as far as I can tell.
Given how uncommon running bin2c seems to be, "optimizing" it may not
be a useful project.
--
Jim
Powered by blists - more mailing lists