linux-kernel - Re: Kconfig 'depend' vs. 'select'

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: <20080427.234221.40346351.davem@davemloft.net>
Date:	Sun, 27 Apr 2008 23:42:21 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	bunk@...nel.org
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Kconfig 'depend' vs. 'select'

From: Adrian Bunk <bunk@...nel.org>
Date: Mon, 28 Apr 2008 09:39:54 +0300

> On Sun, Apr 27, 2008 at 05:45:36PM -0700, David Miller wrote:
> > 
> > I'm trying to stir up interest in solving a problem that seems to pop
> > up frequently. :)
> > 
> > The short story is:
> > 
> > 1) If you say your driver "depend"s on a subsystem providing a set of
> >    interfaces you need, this doesn't work properly if your driver is
> >    marked built-in and that subsystem you need is modular for some
> >    reason.
> >...
> 
> This should work.

It doesn't.

> Can you give an example of the problem you are thinking of?

We've hit this specifically with the intel iwlwifi wireless drivers
over the past week.

> What about "select"?
> 
> That's exactly what it's doing.

Select doesn't enable downstream dependencies, it just blindly turns
it on, non-modular.  That's not what we want at all.

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