Sysfs attributes racing with unregistration

[Alan Stern]

Tejun:

Can you explain the current situation regarding access to sysfs
attributes and possible races with kobject removal?  I have two
questions in particular:

	What happens if one thread calls an attribute's show or
	store method concurrently with another thread unregistering
	the underlying kobject?

	What happens if a thread continues to hold an open fd 
	reference to a sysfs attribute file after the kobject is
	unregistered, and then tries to read or write that fd?

If there are any guarantees about what happens in these situations, I 
can't find them in the kernel source.

And of course, if you can think of any other matters related to this 
topic, please mention them.

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/