diff options
| author | Jeff Layton <jlayton@redhat.com> | 2008-12-23 21:21:33 +0100 |
|---|---|---|
| committer | Trond Myklebust <Trond.Myklebust@netapp.com> | 2008-12-23 21:21:33 +0100 |
| commit | df94f000c46c055cf439f5b92807cd827557ffbc (patch) | |
| tree | c3b224d3ae7c07a5edc3fc804a6d91c8cbdd5cc1 /fs/adfs | |
| parent | LOCKD: Make lockd_up() and lockd_down() exported GPL-only (diff) | |
| download | linux-df94f000c46c055cf439f5b92807cd827557ffbc.tar.xz linux-df94f000c46c055cf439f5b92807cd827557ffbc.zip | |
lockd: convert reclaimer thread to kthread interface
My understanding is that there is a push to turn the kernel_thread
interface into a non-exported symbol and move all kernel threads to use
the kthread API. This patch changes lockd to use kthread_run to spawn
the reclaimer thread.
I've made the assumption here that the extra module references taken
when we spawn this thread are unnecessary and removed them. I've also
added a KERN_ERR printk that pops if the thread can't be spawned to warn
the admin that the locks won't be reclaimed.
In the future, it would be nice to be able to notify userspace that
locks have been lost (probably by implementing SIGLOST), and adding some
good policies about how long we should reattempt to reclaim the locks.
Finally, I removed a comment about memory leaks that I believe is
obsolete and added a new one to clarify the result of sending a SIGKILL
to the reclaimer thread. As best I can tell, doing so doesn't actually
cause a memory leak.
I consider this patch 2.6.29 material.
Signed-off-by: Jeff Layton <jlayton@redhat.com>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Diffstat (limited to 'fs/adfs')
0 files changed, 0 insertions, 0 deletions