aboutsummaryrefslogtreecommitdiffstats
path: root/fs/lockd
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2006-10-02 05:17:53 -0400
committerLinus Torvalds <torvalds@g5.osdl.org>2006-10-02 10:57:18 -0400
commit4a3ae42dc312dbdffee803efaf393421b79f997a (patch)
treed18249c89fc1a5ab273beec1639cde769a0b6e96 /fs/lockd
parent7dcf91ec6698fe8564ad91bbe42740aacaa0d9ee (diff)
[PATCH] knfsd: Correctly handle error condition from lockd_up
If lockd_up fails - what should we expect? Do we have to later call lockd_down? Well the nfs client thinks "no", the nfs server thinks "yes". lockd thinks "yes". The only answer that really makes sense is "no" !! So: Make lockd_up only increment nlmsvc_users on success. Make nfsd handle errors from lockd_up properly. Make sure lockd_up(0) never fails when lockd is running so that the 'reclaimer' call to lockd_up doesn't need to be error checked. Cc: "J. Bruce Fields" <bfields@fieldses.org> Signed-off-by: Neil Brown <neilb@suse.de> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'fs/lockd')
-rw-r--r--fs/lockd/clntlock.c2
-rw-r--r--fs/lockd/svc.c12
2 files changed, 6 insertions, 8 deletions
diff --git a/fs/lockd/clntlock.c b/fs/lockd/clntlock.c
index 6abb465b650f..87e1d03e8267 100644
--- a/fs/lockd/clntlock.c
+++ b/fs/lockd/clntlock.c
@@ -202,7 +202,7 @@ reclaimer(void *ptr)
202 /* This one ensures that our parent doesn't terminate while the 202 /* This one ensures that our parent doesn't terminate while the
203 * reclaim is in progress */ 203 * reclaim is in progress */
204 lock_kernel(); 204 lock_kernel();
205 lockd_up(0); 205 lockd_up(0); /* note: this cannot fail as lockd is already running */
206 206
207 nlmclnt_prepare_reclaim(host); 207 nlmclnt_prepare_reclaim(host);
208 /* First, reclaim all locks that have been marked. */ 208 /* First, reclaim all locks that have been marked. */
diff --git a/fs/lockd/svc.c b/fs/lockd/svc.c
index 448768b52913..3cc369e5693f 100644
--- a/fs/lockd/svc.c
+++ b/fs/lockd/svc.c
@@ -254,15 +254,11 @@ lockd_up(int proto) /* Maybe add a 'family' option when IPv6 is supported ?? */
254 254
255 mutex_lock(&nlmsvc_mutex); 255 mutex_lock(&nlmsvc_mutex);
256 /* 256 /*
257 * Unconditionally increment the user count ... this is
258 * the number of clients who _want_ a lockd process.
259 */
260 nlmsvc_users++;
261 /*
262 * Check whether we're already up and running. 257 * Check whether we're already up and running.
263 */ 258 */
264 if (nlmsvc_pid) { 259 if (nlmsvc_pid) {
265 error = make_socks(nlmsvc_serv, proto); 260 if (proto)
261 error = make_socks(nlmsvc_serv, proto);
266 goto out; 262 goto out;
267 } 263 }
268 264
@@ -270,7 +266,7 @@ lockd_up(int proto) /* Maybe add a 'family' option when IPv6 is supported ?? */
270 * Sanity check: if there's no pid, 266 * Sanity check: if there's no pid,
271 * we should be the first user ... 267 * we should be the first user ...
272 */ 268 */
273 if (nlmsvc_users > 1) 269 if (nlmsvc_users)
274 printk(KERN_WARNING 270 printk(KERN_WARNING
275 "lockd_up: no pid, %d users??\n", nlmsvc_users); 271 "lockd_up: no pid, %d users??\n", nlmsvc_users);
276 272
@@ -302,6 +298,8 @@ lockd_up(int proto) /* Maybe add a 'family' option when IPv6 is supported ?? */
302destroy_and_out: 298destroy_and_out:
303 svc_destroy(serv); 299 svc_destroy(serv);
304out: 300out:
301 if (!error)
302 nlmsvc_users++;
305 mutex_unlock(&nlmsvc_mutex); 303 mutex_unlock(&nlmsvc_mutex);
306 return error; 304 return error;
307} 305}