[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1371493226.9595.5.camel@leira.trondhjem.org>
Date: Mon, 17 Jun 2013 18:20:28 +0000
From: "Myklebust, Trond" <Trond.Myklebust@...app.com>
To: Stanislav Kinsbursky <skinsbursky@...allels.com>
CC: "linux-nfs@...r.kernel.org" <linux-nfs@...r.kernel.org>,
"devel@...nvz.org" <devel@...nvz.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"jlayton@...hat.com" <jlayton@...hat.com>
Subject: Re: [PATCH v2 2/4] SUNRPC: fix races on PipeFS MOUNT notifications
On Tue, 2013-06-11 at 18:39 +0400, Stanislav Kinsbursky wrote:
> Below are races, when RPC client can be created without PiepFS dentries
>
> CPU#0 CPU#1
> ----------------------------- -----------------------------
> rpc_new_client rpc_fill_super
> rpc_setup_pipedir
> mutex_lock(&sn->pipefs_sb_lock)
> rpc_get_sb_net == NULL
> (no per-net PipeFS superblock)
> sn->pipefs_sb = sb;
> notifier_call_chain(MOUNT)
> (client is not in the list)
> rpc_register_client
> (client without pipes dentries)
>
> To fix this patch:
> 1) makes PipeFS mount notification call with pipefs_sb_lock being held.
> 2) releases pipefs_sb_lock on new SUNRPC client creation only after
> registration.
>
> Signed-off-by: Stanislav Kinsbursky <skinsbursky@...allels.com>
> Cc: stable@...r.kernel.org
Hi Stanislav,
This isn't going to apply to the stable kernels without the cleanup
patch. Could you please reorganise this patch series so that the cleanup
comes last.
Thanks,
Trond
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@...app.com
www.netapp.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists