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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Tue, 12 Aug 2014 22:54:17 +0000
From:	Anish Bhatt <anish@...lsio.com>
To:	David Miller <davem@...emloft.net>
CC:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"hch@...radead.org" <hch@...radead.org>,
	Karen Xie <kxie@...lsio.com>,
	Manoj Malviya <manojmalviya@...lsio.com>,
	"jim.epost@...il.com" <jim.epost@...il.com>,
	"sfr@...b.auug.org.au" <sfr@...b.auug.org.au>
Subject: RE: [PATCH net-next] libcxgbi/cxgb4i : Fix ipv6 build failure
 caught with randconfig

>Alternatively, depending upon what IPV6 interfaces you need to use
>in the cxgbi driver, you can potentially move them into the ipv6
>components we've split out to always be statically built into the
>kernel in order to avoid problems of this nature.  See the code
>linked in by the "obj-y +=" rule in net/ipv6/Makefile.

Got it, will fix accordingly.

>> This patch was based on code currently in net-next, and I presumed that would
>> be the correct way to go. I'll change it and rebase to net.

>The net-next tree isn't even open and active at this time, I said last week
>(as I do every single merge window) that I would explicitly announce on
>netdev when the net-next tree is openned.

No, I meant the fix I proposed is currently being used by other code already present in the 
kernel. I'll try and fix that as well.

>But, much more importantly, bug fixes for issues present in 'net'
>should always be targetted to the 'net' tree.

My bad, I was not aware this code made it back to net.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists