linux-kernel - Re: Pure kernel '2.6.37-rc1-00001-ge99d11d' shown as ~-dirty after compilation

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:	Wed, 3 Nov 2010 17:07:00 +0000
From:	trapDoor <trapdoor6@...il.com>
To:	Américo Wang <xiyou.wangcong@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Pure kernel '2.6.37-rc1-00001-ge99d11d' shown as ~-dirty after compilation

On Wed, Nov 3, 2010 at 4:48 PM, Américo Wang <xiyou.wangcong@...il.com> wrote:
> On Tue, Nov 02, 2010 at 08:26:59AM +0000, trapDoor wrote:
>>,Hello,
>>When I run 'make kernelrelease' on freshly cloned Linus' git tree it
>>shows kernel version as: '2.6.37-rc1-00001-ge99d11d' - and that's
>>correct.
>>But after compilation it turned up '2.6.37-rc1-00001-ge99d11d-dirty'.
>>
>>I didn't apply any custom patches to my local tree between 'make
>>kernelrelease' and compilation. What I only added - and before running
>>'make kernelrelease' - were the following Radeon firmware blobs for my
>>graphic card, which I placed in <kernel-source>/firmware/radeon/, in
>>order to compile them in:
>>REDWOOD_me.bin
>>REDWOOD_pfp.bin
>>REDWOOD_rlc.bin
>>
>>That's how I always did and none of the git-kernels I compiled before
>>was referred to as '-dirty' due to the firmware blobs added manually.
>>Also, the kernel version shown by 'make kernelrelease' never differed
>>from the final kernel version after compilation. Of course assuming
>>that no patches were applied in the meantime and no extra string was
>>appended manually to the kernel version.
>>
>>So, what's this '-dirty' about?
>>
>
> That means your git tree is not clean, since you placed new firmwares
> into the source tree.
>
> --
> Live like a child, think like the god.
>

OK, but then 'make kernelrelease' should produce the same '..-dirty'
version, not just '2.6.37-rc1-00001-ge99d11d', shouldn't it?

I always do the following steps in the same order:
1) first I place the firmware files in <kernel-src>/firmware/radeon
2) then I choose appropriate config file and copy it into kernel
source directory
3) then I run 'make oldconfig' and at the end - just before compiling
and installing - 'make kernelrelease'

As I mentioned, for none of the kernels I compiled prior to this
version (either from git or from tarball) 'make kernelrelease'
produced different version name than it came up after compilation.


-- 
Thanks,
Tomasz
--
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/