| 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
| ||
|
Date: Mon, 12 May 2014 13:19:54 -0400 From: Jon Maloy <jon.maloy@...csson.com> To: Willy Tarreau <w@....eu> CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "stable@...r.kernel.org" <stable@...r.kernel.org>, Ying Xue <ying.xue@...driver.com>, Paul Gortmaker <paul.gortmaker@...driver.com>, "David S. Miller" <davem@...emloft.net> Subject: Re: [ 072/143] tipc: fix lockdep warning during bearer initialization On 05/12/2014 01:12 PM, Willy Tarreau wrote: > On Mon, May 12, 2014 at 04:41:00PM +0000, Jon Maloy wrote: >> Sorry, I should have mentioned that it is still only in net-next. >> It is pretty recent. > > OK indeed, got it here for reference : > > https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=7216cd949c9bd56 > > But anyway, what is mentionned in this commit is a number of changes that > happened between 2.6.32 and 3.15, so I hardly see how the tipc_net_lock > is obsolete in 2.6.32 if it does not have all these changes. I have counted > 489 commits between 2.6.32 and 3.15-rc5 touching net/tipc, so surely we > cannot count on what we have to get rid of this lock. > > Am I missing anything ? Ok. I missed the 2.6.32 part. I withdraw my objection. ///jon > > Thanks, > Willy > -- 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/
Powered by blists - more mailing lists