-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am Sonntag, 20. Juni 2004 13:18 schrieb Herbert Xu:
> Oliver Neukum <[EMAIL PROTECTED]> wrote:
> >
> >> synchronize by a lock then it will always see the correct value, since the
> >> unlocking functions -- up() and spin_unlock() -- include write barriers.
> >
> > The issue is not the pointer itself. The problem is the memory the pointer
> > is pointing to. Iff the new pointer is returned the caller can expect that
> > that area of memory is initialised. Therefore the barrier must be before
> > the assignment. If you depend on the lock's barrier there's a window
> > in which the assumption is not necessarily true.
>
> Can you please give a sample execution path that triggers this bug?
I am on x86 which has ordered store. Sorry, you need ppc or something like
that to trigger it. Theoretically you might see it in hub_configure() racing
hub_port_status().
Regards
Oliver
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFA1aE1buJ1a+1Sn8oRAoJkAJ4mr/bvybTqqiFhNRgl9V8POF4IVgCg9bNw
qjjS8yswoWDfSpxnb//fmSs=
=jUPi
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
