From: Jens Axboe <jens.axboe@oracle.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: a.p.zijlstra@chello.nl, trond.myklebust@fys.uio.no
Subject: Re: [PATCH] nfs: fix bdi_unregister() before sb kill
Date: Thu, 17 Sep 2009 21:40:28 +0200 [thread overview]
Message-ID: <20090917194027.GS23126@kernel.dk> (raw)
In-Reply-To: <20090917124233.GJ23126@kernel.dk>
On Thu, Sep 17 2009, Jens Axboe wrote:
> Hi,
>
> This can cause a hang on NFS umount, since the bdi gets pruned before we
> flush any pending dirty IO. Peter, can you check whether it fixes your
> issue?
There's another problem with NFS && backing devices. NFS may call
bdi_destroy() on a bdi without ever called bdi_init(). This was always a
bad idea, now it's an issue.
So, Trond, can I safely add a server->flags private flag to indicate
that we have called bdi_init()? Then nfs_free_server() knows when to
call bdi_destroy(). Seems like the safest fix, since error handling is
currently 'just call nfs_free_server()'.
diff --git a/fs/nfs/client.c b/fs/nfs/client.c
index e350bd6..8ffee33 100644
--- a/fs/nfs/client.c
+++ b/fs/nfs/client.c
@@ -936,6 +936,7 @@ static int nfs_probe_fsinfo(struct nfs_server *server, struct nfs_fh *mntfh, str
error = bdi_init(&server->backing_dev_info);
if (error)
goto out_error;
+ server->flags |= NFS_MOUNT_BDI_INITED;
/* Get some general file system info */
@@ -1021,7 +1022,8 @@ void nfs_free_server(struct nfs_server *server)
nfs_put_client(server->nfs_client);
nfs_free_iostats(server->io_stats);
- bdi_destroy(&server->backing_dev_info);
+ if (server->flags & NFS_MOUNT_BDI_INITED)
+ bdi_destroy(&server->backing_dev_info);
kfree(server);
nfs_release_automount_timer();
dprintk("<-- nfs_free_server()\n");
diff --git a/include/linux/nfs_mount.h b/include/linux/nfs_mount.h
index 4499016..842ef74 100644
--- a/include/linux/nfs_mount.h
+++ b/include/linux/nfs_mount.h
@@ -69,5 +69,6 @@ struct nfs_mount_data {
#define NFS_MOUNT_LOOKUP_CACHE_NONEG 0x10000
#define NFS_MOUNT_LOOKUP_CACHE_NONE 0x20000
#define NFS_MOUNT_NORESVPORT 0x40000
+#define NFS_MOUNT_BDI_INITED 0x80000
#endif
--
Jens Axboe
next prev parent reply other threads:[~2009-09-17 19:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 12:42 Jens Axboe
2009-09-17 19:40 ` Jens Axboe [this message]
2009-09-17 19:47 ` Peter Zijlstra
2009-09-17 19:48 ` Jens Axboe
2009-09-17 23:16 ` Trond Myklebust
2009-09-18 6:40 ` Jens Axboe
2009-09-18 15:02 ` Jens Axboe
2009-09-18 16:19 ` Trond Myklebust
2009-09-18 17:36 ` Jens Axboe
2009-09-18 18:32 ` Jens Axboe
2009-09-18 18:40 ` Trond Myklebust
2009-09-18 18:46 ` Jens Axboe
2009-09-18 20:01 ` Jens Axboe
2009-09-18 20:05 ` Jens Axboe
2009-09-18 20:11 ` Trond Myklebust
2009-09-18 20:16 ` Peter Zijlstra
2009-09-18 20:22 ` Jens Axboe
2009-09-18 20:38 ` Peter Zijlstra
2009-09-18 20:44 ` Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090917194027.GS23126@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome