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] [day] [month] [year] [list]
Message-ID: <20150127223922.GQ26493@n2100.arm.linux.org.uk>
Date:	Tue, 27 Jan 2015 22:39:22 +0000
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Mason <mpeg.blue@...e.fr>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Linux ARM <linux-arm-kernel@...ts.infradead.org>
Subject: Re: Embedded white space in out-of-tree module full pathname

On Tue, Jan 27, 2015 at 10:44:41AM +0100, Mason wrote:
> I'd like some confirmation that this is either not supported, or that
> I'm doing something obviously wrong. (Kernel 3.14 if it matters.)

It's something which isn't going to be supported.

Various things in the make makes it difficult - for example:

module-dirs := $(addprefix _module_,$(KBUILD_EXTMOD))

and as per your example, addprefix will see "/tmp/foo" and "bar/module"
as two separate words.  make has no way to know that these are one
path rather than two separate paths.

See the addprefix documentation in make's info pages, which splits the
second argument by whitespace.

Unlike shell, where you have IFS= which can change the word splitting,
make always uses white space.

-- 
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
--
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