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: <20081017174506.GG2221@kroah.com>
Date:	Fri, 17 Oct 2008 10:45:06 -0700
From:	Greg KH <greg@...ah.com>
To:	Adrian Bunk <bunk@...nel.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC] Kernel version numbering scheme change

On Fri, Oct 17, 2008 at 11:56:04AM +0300, Adrian Bunk wrote:
> On Fri, Oct 17, 2008 at 12:55:44AM -0700, Greg KH wrote:
> > On Fri, Oct 17, 2008 at 09:47:51AM +0300, Adrian Bunk wrote:
> >...
> > > Packages are built in a chroot with the correct release installed.
> > 
> > Then why would this break if they are being built against the correct,
> > older, kernel?
> 
> How could you build userspace "against a kernel"?
> 
> sys_*uname() returns the version of the running kernel.

Great, then why does the build system depend on the running kernel?
Doesn't that sound like a bug?

> > > > and that build would be
> > > > determining things based on the system it is built on, not what it is
> > > > being built for?
> > > 
> > > No.
> > > 
> > > In the example I gave it is OpenSSL that parses the version number of 
> > > the kernel.
> > 
> > The running kernel, with the expectation that this is the kernel it is
> > going to be running on after it is built, right?  Sounds like to ensure
> > this is correct, you better be building it on the kernel that you are
> > going to run it on, or its build process is broken.
> 
> I'm not even sure whether OpenSSL actually does anything with the 
> information: The script comes from the Apache foundation and
> claims to be "Similar to config.guess but much, much smaller."
> 
> BTW: Apache 1.3 seems to ship and use the same script.

Again, depending on the kernel the product is being built on, to
determine a build-time configuration, seems quite broken if you want to
do cross-compilation.

Or you just do native builds, on the kernel you expect to run the
product, and everyone is happy and there are no errors.

thanks,

greg k-h
--
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