linux-kernel - Re: [patch, -git] isdn: hysdn

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:	Wed, 30 Apr 2008 20:30:51 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	den@...nvz.org, linux-kernel@...r.kernel.org
Subject: Re: [patch, -git] isdn: hysdn_procconf.c build fix


* Andrew Morton <akpm@...ux-foundation.org> wrote:

> On Wed, 30 Apr 2008 19:57:40 +0200
> Ingo Molnar <mingo@...e.hu> wrote:
> 
> > Ob'grumpy: this file was not even build-tested by any of the parties 
> > who turned it into upstream commit ac41cfd19b ("isdn: use non-racy 
> > method for proc entries creation").
> 
> That's because this stupidity:
> 
> config HYSDN
>         tristate "Hypercope HYSDN cards (Champ, Ergo, Metro) support (module only)"
>         depends on m && PROC_FS && PCI && BROKEN_ON_SMP
> 
> breaks allmodconfig coverage testing.

yeah. There's a trick though that we use in the x86 tree (and which i'm 
using in a script when queuing up new patches). The following command 
will punch through any Kconfig black holes:

  make drivers/isdn/hysdn/hysdn_procconf.o

(it wont always work as it needs a halfways reasonable .config, but it 
works well enough to be part of my workflow.)

note that there's tons more stuff and dependencies that plain 
allmodconfig does not catch - in this merge window alone i'm at around 
20 fixes so far.

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