| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 10 Sep 2012 19:55:34 +0400 From: Stanislav Kinsbursky <skinsbursky@...allels.com> To: "Myklebust, Trond" <Trond.Myklebust@...app.com> CC: Jeff Layton <jlayton@...hat.com>, "bfields@...ldses.org" <bfields@...ldses.org>, "linux-nfs@...r.kernel.org" <linux-nfs@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "devel@...nvz.org" <devel@...nvz.org> Subject: Re: [PATCH v2] SUNRPC: check current nsproxy before set of node name on client creation 10.09.2012 19:41, Myklebust, Trond пишет: > On Mon, 2012-09-10 at 19:37 +0400, Stanislav Kinsbursky wrote: >> Hi, Trond. >> So, if I understand you right, we can create rpc client (or increase usage >> counter) on NSMPROC_MON call and destroy (or decrease usage counter) on >> NSMPROC_UNMON call. >> Will this solution works? > > The rpc client(s) will need to be per-net-namespace, which complicates > matters a little bit, but yes, creation at NSMPROC_MON, and destruction > at NSMPROC_UNMON should work. > Not really. We already have per-net Lockd data. So, adding one more reference-counted rpc client doesn't look that complicated. Ok, thanks. I'll try to implement this. -- Best regards, Stanislav Kinsbursky -- 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