linux-kernel - Re: [PATCH 1/1] veth: don't free priv->status until dev->destructor (v2)

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: <20090720142542.4fb12c12@nehalam>
Date:	Mon, 20 Jul 2009 14:25:42 -0700
From:	Stephen Hemminger <shemminger@...tta.com>
To:	serue@...ibm.com
Cc:	David Miller <davem@...emloft.net>, containers@...ts.osdl.org,
	sachinp@...ibm.com, netdev@...r.kernel.org, matthltc@...ibm.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] veth: don't free priv->status until dev->destructor
 (v2)

On Wed, 15 Jul 2009 08:50:12 -0700 (PDT)
David Miller <davem@...emloft.net> wrote:

> From: "Serge E. Hallyn" <serue@...ibm.com>
> Date: Fri, 26 Jun 2009 11:24:18 -0500
> 
> > I haven't been able to reproduce the original oops though (been
> > trying to cat the stats sysfs files while rmmoding veth, to no
> > avail, and haven't found an original bug report or testcase), so
> > can't verify whether this patch prevents the original oops.
> 
> If you 'cat' it you're unlikely to trigger the oops.
> 
> You have to hold the sysfs files open, and then elsewhere do the
> rmmod, wait, and then continue with some access to those open sysfs
> file descriptors (f.e. do some reads).
> 
> I'd also need this patch to be against current sources as they'll
> never apply since I did the revert quite some time ago.
> 
> Thanks.


My usual way of doing this is:

#  (sleep 30; cat /sys/class/net/ethX/statistics/tx_bytes) &
# rmmod the_buggy_driver

wait...


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