linux-kernel - Re: linux-next: Tree for Sep 19

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:	Fri, 19 Sep 2014 17:18:45 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Anish Bhatt <anish@...lsio.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	"rdunlap@...radead.org" <rdunlap@...radead.org>
CC:	"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"David S. Miller" <davem@...emloft.net>,
	"James E.J. Bottomley" <JBottomley@...allels.com>
Subject: Re: linux-next: Tree for Sep 19

On 09/19/2014 02:42 PM, Anish Bhatt wrote:
> If you're just bisecting, you probably want my very first commit that started this :
> https://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=c99d667e852766afc755fa4430be64bb94e5ea1c
>
> Essentially, the bnx2 modules would silently disable ipv6 support if ipv6 was
> compiled as a module, but cnic was inbuilt. Then it turned out that the select
> on CNIC would override the tristate for CNIC, causing build failures.
>
> The fix for CNIC caused introduced recursive dependencies, requiring this :
> https://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=5d6be6a5d4864712832822efeb9c2d54e4063949
>
> which further required this :
> https://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=95cd6f488d164de462a8279e802a0ad05c33d167
>
> Turns out this was not enough either, requiring this fix :
> https://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=6a38792ca8a5da28f65dc42eeb73d9a431f8d0fd
>
> and so on and so forth. According to the last message, Randy might be
>   working on a proper fix for this :
> http://www.spinics.net/lists/linux-scsi/msg78416.html
>
> Most of this seems to be that the default configs do not select NET, but select SCSI_FC*
> which used to previously select NET on it's own (via SCSI_NET_LINK), maybe this
> is wrong too ?

Default configurations, as per "make savedefconfig", only record differences to the default.
There will be no "CONFIG_NET=y" in a defconfig if "select NET" configures it automatically.
This is per design to reduce the size of the configuration file. On the downside,
it means that a "simple" change such as "select NET" -> "depends NET" has far reaching
consequences.

Guenter

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