On Mon, Jun 07, 2010 at 11:33:18AM -0400, Jeff Layton wrote: > If someone tries to shut down the laundry_wq while it isn't up it'll > cause an oops. Sorry for getting behind.... I'm not seeing how this can happen: nfs4_state_shutdown() is called from nfsd_last_thread(), which can't be called until after nfsd_create_serv() is called. But nfsd_create_serv() is called after nfs4_state_start(). Oh, I see, I'm overlooking __write_ports_add{fd,xprt}(), which can call nfsd_create_serv() without first calling nfs4_state_start(). Argh. --b. > > Signed-off-by: Jeff Layton <jlayton@xxxxxxxxxx> > --- > fs/nfsd/nfs4state.c | 2 ++ > 1 files changed, 2 insertions(+), 0 deletions(-) > > diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c > index 1176708..fc52920 100644 > --- a/fs/nfsd/nfs4state.c > +++ b/fs/nfsd/nfs4state.c > @@ -4124,6 +4124,8 @@ __nfs4_state_shutdown(void) > void > nfs4_state_shutdown(void) > { > + if (!nfs4_init) > + return; > cancel_rearming_delayed_workqueue(laundry_wq, &laundromat_work); > destroy_workqueue(laundry_wq); > locks_end_grace(&nfsd4_manager); > -- > 1.5.5.6 > -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html