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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 5 Dec 2007 07:25:41 +0100 From: Jarek Poplawski <jarkao2@...pl> To: Jarek Poplawski <jarkao2@...il.com> Cc: Joonwoo Park <joonwpark81@...il.com>, netdev@...r.kernel.org, 'Linux Kernel Mailing List' <linux-kernel@...r.kernel.org> Subject: Re: NET: ASSERT_RTNL in __dev_set_promiscuity makes debug warning On 04-12-2007 23:26, Jarek Poplawski wrote: ... > But, IMHO, blowing ASSERT_RTNL up in a few places shouldn't be much > worse. After all, how long such a debugging code should be kept. It > seems, at least sometimes we should be a bit more confident of how > it's called. I see this won't be done this way, but, if it were, then there is no reason to remove the second: documenting feature of ASSERT_RTNL, so some comment about locking should be added. Jarek P. -- 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