linux-kernel - Re: [linux-dvb] Re: Critical points about kernel 2.6.21 and pseudo-authorities

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: <20070430111414.0eefd4b0.akpm@linux-foundation.org>
Date:	Mon, 30 Apr 2007 11:14:14 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	"Uwe Bugla" <uwe.bugla@....de>
Cc:	Mauro Carvalho Chehab <mchehab@...radead.org>,
	helge.hafting@...el.hist.no, torvalds@...ux-foundation.org,
	linux-kernel@...r.kernel.org, linux-dvb@...uxtv.org
Subject: Re: [linux-dvb] Re: Critical points about kernel 2.6.21 and
 pseudo-authorities

On Mon, 30 Apr 2007 19:25:47 +0200
"Uwe Bugla" <uwe.bugla@....de> wrote:

> I did not manage to at least find one single unresolved module during compilation, and I have been working with this almost fantastic solution with several kernels for months now!

That isn't what Mauro is saying.  What he is saying is that the missing
symbols will not be reported at build time.  The kernel will all link
correctly and will appear to load modules correctly.

See, there's a third mechanism for symbol resolution which is used at
runtime, not at build time: symbol_request().

What Mauro is saying is that these changes will cause symbol_request() to
return different results on some people's setups with different hardware,
causing those setups to fail.

-
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/