netdev - Re: [Xen-devel] Re: [PATCH 3/4] [Net] Support Xen accelerated network plugin modules

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: <1179837868.28562.22.camel@moonstone.uk.level5networks.com>
Date:	Tue, 22 May 2007 13:44:28 +0100
From:	Kieran Mansley <kmansley@...arflare.com>
To:	Keir Fraser <keir@...source.com>
Cc:	Stephen Hemminger <shemminger@...ux-foundation.org>,
	muli@...ibm.com, netdev@...r.kernel.org,
	xen-devel@...ts.xensource.com, herbert@...dor.apana.org.au
Subject: Re: [Xen-devel] Re: [PATCH 3/4] [Net] Support Xen accelerated
	network plugin modules

On Tue, 2007-05-22 at 08:48 +0100, Keir Fraser wrote:
> 
> 
> On 22/5/07 08:28, "Kieran Mansley" <kmansley@...arflare.com> wrote:
> 
> > On Tue, 2007-05-22 at 08:15 +0100, Kieran Mansley wrote:
> >> RCU on its own wouldn't
> >> prevent the accelerated plugin being unloaded while netfront was using
> >> one of the hooks.
> > 
> > Hmm, actually I think it could be used to do that.  I'll take a look.
> 
> Eagerly zap the function pointers, then wait one RCU period so every CPU
> goes through a quiescent point before unloading the module?
> 
>  -- Keir

Am I right in thinking that if one of the functions that was protected
by RCU was to block, that would be a bad thing?  Clearly the data path
hooks can't/don't block, but I'm not sure it's so obvious for things
like probing a new device. 

Kieran

-
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