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]

Date:	Mon, 13 Nov 2006 12:54:42 -0600
From:	Paul Fulghum <paulkf@...rogate.com>
To:	Krzysztof Halasa <khc@...waw.pl>
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

Krzysztof Halasa wrote:
> I remember something actually did "won the approval". Don't remember
> the details but I think it included conditional compilation, not
> changing CONFIG_* macros (using different name(s) instead, just not
> starting with "CONFIG_"), and IIRC no changes to Kconfigs.

It's been a while so I don't remember the details
of each suggested fix. The fixes that came closest to
being accepted changed the Kconfigs.

> At least I don't remember any objections to that last version so
> I assumed it's closed.
> 
> Perhaps it was just a dream, who knows :-)

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

After a few weeks of that, I gave up.

Since the only problem is compile errors with
a broken kernel configuration, I was willing to
go with the flow and leave it in the current
functional state as it has been for years.

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

But since we seem stuck in a state where real fixes
are not allowed, and this breakage is constantly reintroduced,
the best thing may be to allow the breakage and I can
provide patches to customers to get things working again.

My preference would be to either fix the warnings (which
I've tried) or leave things in a working state (which
I've also tried), but neither option seems to be allowed.

-- 
Paul Fulghum
Microgate Systems, Ltd.
-
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/