[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHQdGtR8eH-rz3=4uBU=MjrXBUKhrRFO1rsjKqSxD_131MoTFQ@mail.gmail.com>
Date: Wed, 3 Sep 2014 18:18:16 -0400
From: Trond Myklebust <trond.myklebust@...marydata.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Linux Kernel mailing list <linux-kernel@...r.kernel.org>,
Stable Tree <stable@...r.kernel.org>,
Stanislav Kinsbursky <skinsbursky@...allels.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: [PATCH 3.14 83/88] NFS: Fix /proc/fs/nfsfs/servers and /proc/fs/nfsfs/volumes
On Wed, Sep 3, 2014 at 6:05 PM, Greg Kroah-Hartman
<gregkh@...uxfoundation.org> wrote:
> 3.14-stable review patch. If anyone has any objections, please let me know.
>
> ------------------
>
> From: "Eric W. Biederman" <ebiederm@...ssion.com>
>
> commit 65b38851a17472d31fec9019fc3a55b0802dab88 upstream.
>
> The usage of pid_ns->child_reaper->nsproxy->net_ns in
> nfs_server_list_open and nfs_client_list_open is not safe.
>
> /proc for a pid namespace can remain mounted after the all of the
> process in that pid namespace have exited. There are also times
> before the initial process in a pid namespace has started or after the
> initial process in a pid namespace has exited where
> pid_ns->child_reaper can be NULL or stale. Making the idiom
> pid_ns->child_reaper->nsproxy a double whammy of problems.
>
> Luckily all that needs to happen is to move /proc/fs/nfsfs/servers and
> /proc/fs/nfsfs/volumes under /proc/net to /proc/net/nfsfs/servers and
> /proc/net/nfsfs/volumes and add a symlink from the original location,
> and to use seq_open_net as it has been designed.
>
> Cc: Trond Myklebust <trond.myklebust@...marydata.com>
> Cc: Stanislav Kinsbursky <skinsbursky@...allels.com>
> Signed-off-by: "Eric W. Biederman" <ebiederm@...ssion.com>
> Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
>
...and ditto. Please hold off applying until the commit is fixed in upstream.
--
Trond Myklebust
Linux NFS client maintainer, PrimaryData
trond.myklebust@...marydata.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