linux-kernel - Re: [BUG] 2.6.29-rc* QinQ vlan trunking regression

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]

Message-ID: <49AF687D.9080708@trash.net>
Date:	Thu, 05 Mar 2009 06:51:57 +0100
From:	Patrick McHardy <kaber@...sh.net>
To:	Bart Trojanowski <bart@...ie.net>
CC:	David Miller <davem@...emloft.net>, greearb@...delatech.com,
	shemminger@...tta.com, dada1@...mosbay.com,
	frank.blaschka@...ibm.com, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [BUG] 2.6.29-rc* QinQ vlan trunking regression

Bart Trojanowski wrote:
>>> As analyzed by Patrick McHardy, vlan needs to reset it's
>>> netdev_ops pointer in it's ->init() function but this
>>> leaves the compat method pointers stale.
>>>
>>> Add a netdev_resync_ops() and call it from the vlan code.
>> <snip>
>>>  include/linux/netdevice.h |    1 +
>>>  net/8021q/vlan_dev.c      |    1 +
>>>  net/core/dev.c            |   54 +++++++++++++++++++++++++++-----------------
>>>  3 files changed, 35 insertions(+), 21 deletions(-)
>> I tried this patch onto v2.6.29-rc7-3-g559595a, but I still get a crash.
>> I assume that this worked for you, so I am not putting much faith in my
>> results at this late hour.  I'll confirm tomorrow morning that it's not
>> something else.
> 
> ... if you're interested, here is the Oops.  And like I said, I'll
> retest tomorrow.

Thanks, I'll try to reproduce it here.
--
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/