From: "J. Bruce Fields" <bfields@fieldses.org>
To: Weng Meiling <wengmeiling.weng@huawei.com>
Cc: stable@vger.kernel.org, greg@kroah.com, lizefan@huawei.com,
skinsbursky@parallels.com, h.huangqiang@huawei.com,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH v2 3.4 0/9] fix the NULL pointer when use nfs in diferent net ns
Date: Sun, 4 May 2014 08:30:11 -0400 [thread overview]
Message-ID: <20140504123011.GE21635@fieldses.org> (raw)
In-Reply-To: <1398825824-6360-1-git-send-email-wengmeiling.weng@huawei.com>
ACK to these for stable.--b.
On Wed, Apr 30, 2014 at 10:43:35AM +0800, Weng Meiling wrote:
> After 3.4 stable apply commit f7fb86c6e639(nfsd: use "init_net"
> for portmapper). When starting NFSd in a non init_net network
> namespace will trigger kernel panic. Because RPCBIND client
> will be NULL when register RPC service with the local portmapper
> in svc_addsock(). This new bug also exists in 3.8, but disappears
> after patch commit 11f779421a39("containerize NFSd filesystem") in
> 3.9.
>
> So backport Stanislav's patches from 3.8 and 3.9 to cleanup init_net
> reference, and get proper network namespace from superblock instead of
> using hard-coded "init_net" to make NFSd keep using a consistent network
> namespace all the time to resolve the bug.
>
> After this patchset, testing NFS in different network namespace will
> not trigger kernel panic any more, and other NFS client can use the
> NFS server's shared files normally which was started in init_net namespace.
>
> v1->v2:
> - no commit 7fb86c6e639(nfsd: use "init_net" for portmapper) which has been
> apply to 3.4 stable in the first version
> - one more fix patch commit 3064639423c4(nfsd: check passed socket's net matches
> NFSd superblock's one) for commit 11f779421a39("nfsd: containerize NFSd filesystem")
> - fix build error for commit db6e182c17cb(nfsd: pass net to nfsd_init_socks())
>
> Stanislav Kinsbursky (9):
> nfsd: pass net to nfsd_init_socks()
> nfsd: pass net to nfsd_startup() and nfsd_shutdown()
> nfsd: pass net to nfsd_create_serv()
> nfsd: pass net to nfsd_svc()
> nfsd: pass net to nfsd_set_nrthreads()
> nfsd: pass net to __write_ports() and down
> nfsd: pass proper net to nfsd_destroy() from NFSd kthreads
> nfsd: containerize NFSd filesystem
> nfsd: check passed socket's net matches NFSd superblock's one
>
> fs/nfsd/nfsctl.c | 62 +++++++++++++++++++++++++++++-------------
> fs/nfsd/nfsd.h | 6 ++--
> fs/nfsd/nfssvc.c | 41 ++++++++++++++--------------
> include/linux/sunrpc/svcsock.h | 1 +
> net/sunrpc/svcsock.c | 16 +++++++++++
> 5 files changed, 83 insertions(+), 43 deletions(-)
>
> --
> 1.8.2.2
>
>
next prev parent reply other threads:[~2014-05-04 12:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5359B8F0.8030201@huawei.com>
[not found] ` <1398409948-10180-1-git-send-email-wangyijing@huawei.com>
2014-04-30 2:43 ` [PATCH v2 3.4 0/9] fix the NULL pointer when use nfs in diferent net ns Weng Meiling
2014-04-30 2:43 ` [PATCH v2 3.4 1/9] nfsd: pass net to nfsd_init_socks() Weng Meiling
2014-04-30 2:43 ` [PATCH v2 3.4 2/9] nfsd: pass net to nfsd_startup() and nfsd_shutdown() Weng Meiling
2014-04-30 2:43 ` [PATCH v2 3.4 3/9] nfsd: pass net to nfsd_create_serv() Weng Meiling
2014-04-30 2:43 ` [PATCH v2 3.4 4/9] nfsd: pass net to nfsd_svc() Weng Meiling
2014-04-30 2:43 ` [PATCH v2 3.4 5/9] nfsd: pass net to nfsd_set_nrthreads() Weng Meiling
2014-04-30 2:43 ` [PATCH v2 3.4 6/9] nfsd: pass net to __write_ports() and down Weng Meiling
2014-04-30 2:43 ` [PATCH v2 3.4 7/9] nfsd: pass proper net to nfsd_destroy() from NFSd kthreads Weng Meiling
2014-04-30 2:43 ` [PATCH v2 3.4 8/9] nfsd: containerize NFSd filesystem Weng Meiling
2014-04-30 2:43 ` [PATCH v2 3.4 9/9] nfsd: check passed socket's net matches NFSd superblock's one Weng Meiling
2014-05-04 12:30 ` J. Bruce Fields [this message]
2014-06-09 23:49 ` [PATCH v2 3.4 0/9] fix the NULL pointer when use nfs in diferent net ns Greg KH
[not found] ` <1398841733-10144-1-git-send-email-rui.xiang@huawei.com>
2014-06-05 4:15 ` pending 3.4.x backported patches Greg KH
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=20140504123011.GE21635@fieldses.org \
--to=bfields@fieldses.org \
--cc=greg@kroah.com \
--cc=h.huangqiang@huawei.com \
--cc=linux-nfs@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=skinsbursky@parallels.com \
--cc=stable@vger.kernel.org \
--cc=wengmeiling.weng@huawei.com \
/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;
as well as URLs for NNTP newsgroup(s).