linux-kernel - Re: Unfortunate infinite make recursion

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: <20070923060335.GA22208@uranus.ravnborg.org>
Date:	Sun, 23 Sep 2007 08:03:35 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Oleg Verych <olecom@...wer.upol.cz>
Cc:	Jan Engelhardt <jengelh@...putergmbh.de>, zippel@...ux-m68k.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Unfortunate infinite make recursion

> > Please Oleg.
> > You know very well that most people will not have their kernel src RO.
> 
> Sure, if it will be not comfortable.
> 
> But if kbuild deals with this transparently, it must be OK. Brokenness
> due to binutils, kbuild, root user bugs won't garbage source. Only thing
> to ask from experienced users *and* kernel developers, is
> `useradd kbuild`, everything else will not bother anybody.
Better would be to fix the bugs where we today clobber the sources.
Care to point out the exact cases you see.

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