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]
Message-ID: <20101103164840.GC4683@hack>
Date:	Thu, 4 Nov 2010 00:48:40 +0800
From:	Américo Wang <xiyou.wangcong@...il.com>
To:	trapDoor <trapdoor6@...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 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.
 
--
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