netdev - Re: NULL pointer dereference in veth_stats

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1357314320.1678.1414.camel@edumazet-glaptop>
Date:	Fri, 04 Jan 2013 07:45:20 -0800
From:	Eric Dumazet <erdnetdev@...il.com>
To:	Tom Parkin <tparkin@...alix.com>
Cc:	netdev <netdev@...r.kernel.org>
Subject: Re: NULL pointer dereference in veth_stats_one

On Fri, 2013-01-04 at 10:59 +0000, Tom Parkin wrote:
> Hi list,
> 
> I recently tripped over a NULL pointer dereference in the veth driver.
> I'm running a 3.8.0_rc1 (updated from net-next git tree this morning)
> on an Athlon 64 X2 machine running a 32 bit kernel.  To trigger the
> oops I simply created a veth interface as follows:
> 
>         ip link add name ve0 type veth peer name ve1
> 
> I did a little digging in the git history and I note that veth
> statistics changed a little with commit 2681128f0ced8aa4.  I tried
> reverting that commit in my tree, which made the oops go away again.
> 
> Thanks,
> Tom

Thanks Tom, I'll fix this.


--
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