linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanislav Kinsbursky <skinsbursky@parallels.com>
To: Simo Sorce <simo@redhat.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
	"bfields@redhat.com" <bfields@redhat.com>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 3/4] SUNRPC: Add RPC based upcall mechanism for RPCGSS auth
Date: Tue, 22 May 2012 19:23:05 +0400	[thread overview]
Message-ID: <4FBBAF59.5070000@parallels.com> (raw)
In-Reply-To: <1337699906.16840.192.camel@willson.li.ssimo.org>

On 22.05.2012 19:18, Simo Sorce wrote:
> On Tue, 2012-05-22 at 19:10 +0400, Stanislav Kinsbursky wrote:
>> On 22.05.2012 18:58, Simo Sorce wrote:
>>> On Tue, 2012-05-22 at 17:32 +0400, Stanislav Kinsbursky wrote:
>>>> It actually means, that no hard-coded init_net references should appear - and
>>>> that's all. Required network context have to be taken from currently existent
>>>> objects (like RPC client, RPC service, etc) and, if not available (it's very
>>>> rare case - like NFS mount call), from current->nsproxy->net_ns.
>>>> You don't need to do anything special except this.
>>>> There will be a problem with your patches in container, because you are using
>>>> unix socket. But this problem is not in your patches but in unix sockets
>>>> themselves. So don't worry about it.
>>>
>>> Can you tell me if the attached patches are all you think is needed ?
>>> If they are, I'll squash them in with other fixes and will send out a
>>> new patch set.
>>>
>>
>> Yep, looks good.
>> Would be great, if you'll fix a couple of minor issues:
>> 1) rename "xprt_net" to "net" in prototypes (just to make things look in one
>> style with other places in SUNRPC layer)
>
> TBH, I thikn using 'net' is the worst name you guys could come up with,
> try to 'git grep net' to see what I mean, but whatever, the damage is
> already done, I'll change it.
>

The reason for the simple name was that we don't care, where we gained this net: 
was it transport or whatever.
IOW, "xprt_net" doesn't carrying any required information comparing to "net" in 
this case.

>> 2) define net variable on stack in svcauth_gss_proxy_init() (looks simpler):
>>
>> +static int svcauth_gss_proxy_init(struct svc_rqst *rqstp,
>> +                       struct rpc_gss_wire_cred *gc, __be32 *authp)
>> ....
>> +       struct net *net = rqstp->rq_xprt->xpt_net;
>> +       struct sunrpc_net *sn = net_generic(net, sunrpc_net_id);
>> ....
>> +       status = gssp_accept_sec_context_upcall(net,&ud);
>
> Heh, that is what I did at first, then changed. Works for me, I'll
> include these changes in the new patchset.
>

Thanks, Simo.

> Simo.
>


-- 
Best regards,
Stanislav Kinsbursky

  reply	other threads:[~2012-05-22 15:23 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15 13:12 [PATCH 0/4] Add support for new upcall mechanism for nfsd Simo Sorce
2012-05-15 13:12 ` [PATCH 1/4] SUNRPC: conditionally return endtime from import_sec_context Simo Sorce
2012-05-21 21:52   ` J. Bruce Fields
2012-05-15 13:12 ` [PATCH 2/4] SUNRPC: Document a bit RPCGSS handling in the NFS Server Simo Sorce
2012-05-21 21:55   ` J. Bruce Fields
2012-05-22  0:37     ` Simo Sorce
2012-05-15 13:12 ` [PATCH 3/4] SUNRPC: Add RPC based upcall mechanism for RPCGSS auth Simo Sorce
2012-05-22 12:47   ` J. Bruce Fields
2012-05-22 13:00     ` Simo Sorce
2012-05-22 13:17       ` Stanislav Kinsbursky
2012-05-22 13:22         ` Simo Sorce
2012-05-22 13:32           ` Stanislav Kinsbursky
2012-05-22 14:20             ` J. Bruce Fields
2012-05-22 14:44               ` Stanislav Kinsbursky
2012-05-22 15:07                 ` J. Bruce Fields
2012-05-22 15:16                   ` Simo Sorce
2012-05-22 15:31                     ` J. Bruce Fields
2012-05-22 15:44                       ` Simo Sorce
2012-05-22 15:19                   ` Stanislav Kinsbursky
2012-05-22 18:11                     ` J. Bruce Fields
2012-05-22 18:41                       ` Stanislav Kinsbursky
2012-05-22 14:58             ` Simo Sorce
2012-05-22 15:10               ` Stanislav Kinsbursky
2012-05-22 15:18                 ` Simo Sorce
2012-05-22 15:23                   ` Stanislav Kinsbursky [this message]
2012-05-22 13:00     ` Stanislav Kinsbursky
2012-05-22 15:02   ` J. Bruce Fields
2012-05-22 15:15     ` Simo Sorce
2012-05-22 15:29       ` J. Bruce Fields
2012-05-22 15:40         ` Simo Sorce
2012-05-22 22:49           ` J. Bruce Fields
2012-05-22 22:52             ` Simo Sorce
2012-05-22 15:03   ` J. Bruce Fields
2012-05-22 15:12     ` Simo Sorce
2012-05-22 15:24       ` J. Bruce Fields
2012-05-22 15:36         ` Simo Sorce
2012-05-15 13:12 ` [PATCH 4/4] SUNRPC: Use gssproxy upcall for nfsd's RPCGSS authentication Simo Sorce
2012-05-22 22:48   ` J. Bruce Fields
2012-05-24  4:31     ` Simo Sorce
2012-05-24 11:08       ` J. Bruce Fields
2012-05-24 13:19         ` Simo Sorce
2012-05-25 14:05           ` J. Bruce Fields
2012-05-25 15:37             ` Simo Sorce
  -- strict thread matches above, loose matches on Subject: below --
2012-05-25 22:09 [PATCH 0/4] Add support for new RPCSEC_GSS upcall mechanism for nfsd Simo Sorce
2012-05-25 22:09 ` [PATCH 3/4] SUNRPC: Add RPC based upcall mechanism for RPCGSS auth Simo Sorce

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=4FBBAF59.5070000@parallels.com \
    --to=skinsbursky@parallels.com \
    --cc=bfields@fieldses.org \
    --cc=bfields@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=simo@redhat.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).