Kernel Newbies archive on
 help / color / Atom feed
From: "Valdis Klētnieks" <>
To: wuzhouhui <>
Subject: Re: how to determine whether the source code is same between two kernels
Date: Wed, 08 May 2019 09:43:22 -0400
Message-ID: <28922.1557323002@turing-police> (raw)
In-Reply-To: <>

[-- Attachment #1.1: Type: text/plain, Size: 999 bytes --]

On Wed, 08 May 2019 16:52:46 +0800, wuzhouhui said:
> Suppose I have two kernels, one is A.B.C build by people Tom. And
> the other is A.B.C build by Jerry. The source code have been deleted
> after kernel is build and installed. Now I want to know whether the
> source code of these two kernel is the same (even if they have the same
> name). All I have is binaries (e.g. vmlinux, config, *.ko,
> Is it possible?

The problem is that I can build my kernel with gcc5 (or even a gcc4.mumble),
and the binaries are going to be different than what the same exact source tree
produces with gcc 9.1.1.

Of course, the *correct* solution is to hold both Tom and Jerry to the
requirements of the GPL, and force them to give you the kernel source trees
that went into those kernels that they distributed, and then compare the trees.

What? You say neither one can actually do so? Then why are you accepting and
using kernels from them, rather than shunning them as the GPL violators they

[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

Kernelnewbies mailing list

  parent reply index

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-08  8:52 wuzhouhui
2019-05-08  9:25 ` Greg KH
2019-05-08  9:43   ` wuzhouhui
2019-05-08 10:08     ` greg kh
2019-05-08 13:43 ` Valdis Klētnieks [this message]
2019-05-11  2:11 ` Aruna Hewapathirane
2019-05-11  3:58   ` Valdis Klētnieks
2019-05-11 13:20     ` Aruna Hewapathirane
2019-05-11 13:53       ` Valdis Klētnieks
2019-05-11 23:47         ` chiachen

Reply instructions:

You may reply publically to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=28922.1557323002@turing-police \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Kernel Newbies archive on

Archives are clonable:
	git clone --mirror kernelnewbies/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 kernelnewbies kernelnewbies/ \
	public-inbox-index kernelnewbies

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone public-inbox