summaryrefslogtreecommitdiff
path: root/fs/namespace.c
diff options
context:
space:
mode:
authorChristian Borntraeger <borntraeger@de.ibm.com>2008-12-02 11:16:03 +0100
committerAvi Kivity <avi@redhat.com>2008-12-31 16:55:44 +0200
commite3a2a0d4e5ace731e60e2eff4fb7056ecb34adc1 (patch)
tree87626c198c57dda52979c01f5c781e32ba370e5c /fs/namespace.c
parente93353c93a3ba4215633ce930784f40a4e94e3f9 (diff)
downloadlinux-3.10-e3a2a0d4e5ace731e60e2eff4fb7056ecb34adc1.tar.gz
linux-3.10-e3a2a0d4e5ace731e60e2eff4fb7056ecb34adc1.tar.bz2
linux-3.10-e3a2a0d4e5ace731e60e2eff4fb7056ecb34adc1.zip
anon_inodes: use fops->owner for module refcount
There is an imbalance for anonymous inodes. If the fops->owner field is set, the module reference count of owner is decreases on release. ("filp_close" --> "__fput" ---> "fops_put") On the other hand, anon_inode_getfd does not increase the module reference count of owner. This causes two problems: - if owner is set, the module refcount goes negative - if owner is not set, the module can be unloaded while code is running This patch changes anon_inode_getfd to be symmetric regarding fops->owner handling. I have checked all existing users of anon_inode_getfd. Noone sets fops->owner, thats why nobody has seen the module refcount negative. The refcounting was tested with a patched and unpatched KVM module.(see patch 2/2) I also did an epoll_open/close test. Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com> Reviewed-by: Davide Libenzi <davidel@xmailserver.org> Signed-off-by: Avi Kivity <avi@redhat.com>
Diffstat (limited to 'fs/namespace.c')
0 files changed, 0 insertions, 0 deletions