summaryrefslogtreecommitdiffstats
path: root/drivers/hwmon/hwmon-vid.c
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2013-09-08 18:13:49 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2013-09-08 18:13:49 -0700
commite5c832d5558826cc6e9a24746cfdec8e7780063a (patch)
tree2b40ee4754dc80b81018ac91282ade4bdcd3c562 /drivers/hwmon/hwmon-vid.c
parent0d98439ea3c6ffb2af931f6de4480e744634e2c5 (diff)
downloadtalos-obmc-linux-e5c832d5558826cc6e9a24746cfdec8e7780063a.tar.gz
talos-obmc-linux-e5c832d5558826cc6e9a24746cfdec8e7780063a.zip
vfs: fix dentry RCU to refcounting possibly sleeping dput()
This is the fix that the last two commits indirectly led up to - making sure that we don't call dput() in a bad context on the dentries we've looked up in RCU mode after the sequence count validation fails. This basically expands d_rcu_to_refcount() into the callers, and then fixes the callers to delay the dput() in the failure case until _after_ we've dropped all locks and are no longer in an RCU-locked region. The case of 'complete_walk()' was trivial, since its failure case did the unlock_rcu_walk() directly after the call to d_rcu_to_refcount(), and as such that is just a pure expansion of the function with a trivial movement of the resulting dput() to after 'unlock_rcu_walk()'. In contrast, the unlazy_walk() case was much more complicated, because not only does convert two different dentries from RCU to be reference counted, but it used to not call unlock_rcu_walk() at all, and instead just returned an error and let the caller clean everything up in "terminate_walk()". Happily, one of the dentries in question (called "parent" inside unlazy_walk()) is the dentry of "nd->path", which terminate_walk() wants a refcount to anyway for the non-RCU case. So what the new and improved unlazy_walk() does is to first turn that dentry into a refcounted one, and once that is set up, the error cases can continue to use the terminate_walk() helper for cleanup, but for the non-RCU case. Which makes it possible to drop out of RCU mode if we actually hit the sequence number failure case. Acked-by: Al Viro <viro@zeniv.linux.org.uk> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers/hwmon/hwmon-vid.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud