linux-kernel - Re: [PATCH] Re: linux-2.6.19-rc5-g088406bc build #120 failed

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: <m3ac2v6phw.fsf@defiant.localdomain>
Date:	Mon, 13 Nov 2006 21:49:47 +0100
From:	Krzysztof Halasa <khc@...waw.pl>
To:	Paul Fulghum <paulkf@...rogate.com>
Cc:	Jeff Garzik <jeff@...zik.org>,
	Toralf Förster <toralf.foerster@....de>,
	linux-kernel@...r.kernel.org, Andrew Morton <akpm@...l.org>
Subject: Re: [PATCH] Re: linux-2.6.19-rc5-g088406bc build #120 failed

Paul Fulghum <paulkf@...rogate.com> writes:

> We were in a perpetual state of:
>
> 1. supply patch
> 2. get criticism from new person just joining thread
> 3. change patch to address criticism
> 4. goto #1

Right, the description fits. OTOH I recall the criticism had a fair
amount of merit. That's how the things work here. Been there many
times BTW.

>> Nevertheless a fix outlined above would be acceptable, wouldn't it?
>
> It breaks things by forcing the customer to include code
> that is not required. That is an issue for embedded systems.

Nope, the fix which didn't change Kconfig and just assumed HDLC=m and
SYNCLINK*=y => HDLC is not available. I.e., the one with

#if defined(CONFIG_HDLC_MODULE) &&/|| defined(CONFIG_SYNCLINK*something)
#define CONFIG_HDLC something

changed into

#if defined(CONFIG_HDLC_MODULE) &&/|| defined(CONFIG_SYNCLINK*something)
#define USE_HDLC something
        ^^^^^^^^

> But since we seem stuck in a state where real fixes
> are not allowed, and this breakage is constantly reintroduced,

It may look like that sometimes but it's not real. Anyway I think
everyone would benefit from the correct fix and the issue wouldn't
come again. Having looked at it I'd fix it myself but I'm pretty
sure you still have the old patch (which changes CONFIG_ macros
outside Kconfig, I mean in .c files) and it could be trivially
modified then applied (and perhaps tested with real hardware if
needed).
-- 
Krzysztof Halasa
-
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/