Messages in this thread | | | Date | Thu, 9 Jan 2014 11:15:10 +0400 | From | Stanislav Kinsbursky <> | Subject | Re: [PATCH] nfsd: check passed socket's net matches NFSd superblock's one |
| |
04.01.2014 02:22, J. Bruce Fields пишет: > On Mon, Dec 30, 2013 at 05:23:59PM +0300, Stanislav Kinsbursky wrote: >> There could be a case, when NFSd file system is mounted in network, different >> to socket's one, like below: >> >> "ip netns exec" creates new network and mount namespace, which duplicates NFSd >> mount point, created in init_net context. And thus NFS server stop in nested >> network context leads to RPCBIND client destruction in init_net. >> Then, on NFSd start in nested network context, rpc.nfsd process creates socket >> in nested net and passes it into "write_ports", which leads to RPCBIND sockets >> creation in init_net context because of the same reason (NFSd monut point was >> created in init_net context). An attempt to register passed socket in nested >> net leads to panic, because no RPCBIND client present in nexted network >> namespace. > > So it's the attempt to use a NULL ->rpcb_local_clnt4? >
Correct.
-- Best regards, Stanislav Kinsbursky -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |