From: "J. Bruce Fields" <bfields@fieldses.org>
To: Simo Sorce <simo@redhat.com>
Cc: "J. Bruce Fields" <bfields@redhat.com>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 3/4] SUNRPC: Add RPC based upcall mechanism for RPCGSS auth
Date: Tue, 22 May 2012 18:49:04 -0400 [thread overview]
Message-ID: <20120522224904.GB6435@fieldses.org> (raw)
In-Reply-To: <1337701251.16840.201.camel@willson.li.ssimo.org>
On Tue, May 22, 2012 at 11:40:51AM -0400, Simo Sorce wrote:
> On Tue, 2012-05-22 at 11:29 -0400, J. Bruce Fields wrote:
> > On Tue, May 22, 2012 at 11:15:22AM -0400, Simo Sorce wrote:
> > > On Tue, 2012-05-22 at 11:02 -0400, J. Bruce Fields wrote:
> > > > This seems
> > > > likely to break in subtle ways if we ever change one of those constants
> > > > to not be a multiple of a large enough power of 2. And makes the memory
> > > > handling a little more obscure. I'd rather just allocate those
> > > > separately if that's the choice.
> > >
> > > I do not see why it would break, the only limit we have is the total
> > > size of the kmembuf.
> >
> > Oh, just because the svc_cred at the end wouldn't be aligned nicely any
> > more. Doesn't that bother some architectures?
>
> Ah yeah I see, indeed some architecture require memory to be aligned.
> I will change that code back to kmallocs, which is what I always
> preferred anyway.
>
> > > > Whatever, I don't really care how the various xdr_netobj->data's are
> > > > allocated, honestly there's no crusade to eliminate kmalloc()'s, I'll
> > > > only object in a case (like the struct svc_cred field above) where it
> > > > seems obviously unnecessary.
> > >
> > > Ok, so what should I do ?
> > > I can remove the static allocation and let the code allocate the data
> > > with kmalloc, in the xdr unmarshalling code.
> > > Whatever you like best.
> >
> > Just embed the svc_cred:
> >
> > > > - struct svc_cred *creds;
> > > > + struct svc_cred creds;
>
> Can't do, it needs to be allocated, because we steal it in scvauth_gss.c
Are you sure? Looks to me like it's only the group list that's "stolen"
there, the rest is copied.
--b.
>
> > and handle the rest whichever way seems cleanest to you.
>
> Ok.
>
> Simo.
>
> --
> Simo Sorce * Red Hat, Inc * New York
>
next prev parent reply other threads:[~2012-05-22 22:49 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
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 [this message]
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=20120522224904.GB6435@fieldses.org \
--to=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).