| 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: Fri, 15 May 2009 11:19:46 +0400 From: "Alexander V. Lukyanov" <lav@...is.ru> To: Jarek Poplawski <jarkao2@...il.com> Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org Subject: Re: 2.6.29.1: unregister_netdevice problem On Sun, May 10, 2009 at 02:46:41PM +0200, Jarek Poplawski wrote: > On Sun, May 10, 2009 at 11:35:59AM +0400, Alexander V. Lukyanov wrote: > > On Fri, May 08, 2009 at 10:46:28AM +0000, Jarek Poplawski wrote: > > > I can't see anything suspicious for now, except these UDP and TCP > > > warnings. Did you see similar messages with 2.6.27? Btw., could this > > > > Yes. Such messages show up with any kernel version. > > > > > eth0.987 be "connected" with any of this traffic? (IP# ?) > > > > No, eth0.987 is only used for traffic output. > > > > BTW, it seems that only actively used vlan interfaces have the problem > > (even when the traffic stops). Other vlan interfaces with little traffic > > can be removed with no problems. > > OK, I'll try to look around this, but how about trying 2.6.28.10 in > the meantime? It could limit "a bit" the number of places/lines. Looks like 2.6.28.10 does not have this refcnt problem. Also, after I have reversed net/ipv4/route.c changes from 2.6.29, the problem does not occur either. -- Alexander.. -- 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