public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Lukas Hejtmanek <xhejtman@ics.muni.cz>
To: Kevin Coffman <kwc@citi.umich.edu>
Cc: NFSv3 list <linux-nfs@vger.kernel.org>,
	nfsv4@linux-nfs.org, Jeff Layton <jlayton@redhat.com>
Subject: Re: ANNOUNCE: nfs-utils-1.2.2 released.
Date: Tue, 9 Mar 2010 16:53:10 +0100	[thread overview]
Message-ID: <20100309155310.GR19154@ics.muni.cz> (raw)
In-Reply-To: <4d569c331003090718j6cde9853o6142b2fd2900248e@mail.gmail.com>

On Tue, Mar 09, 2010 at 10:18:58AM -0500, Kevin Coffman wrote:
> I've built nfs-utils with and without  --disable-tirpc and don't see
> this problem.
> =

> It could be a bug, but I would think that other [Debian and other]
> testers would have already hit it.
> =

> I'm concerned that perhaps your build issues may have somehow
> introduced a [bad] mix of headers?  (i.e. were things built using the
> libgssglue headers, or the Kerberos headers?)

I have both. If I remove gssglue headers, it still faults. If I remove
kerberos headers, it does not even compile.

I believe, that it has the following problem.

gssd calls gss_acquire_cred, it calls the one from libgssapi_krb5.so.2. =

This gss_acquire_cred filss in gss_union_cred_t structure. =

gssd calls gss_set_allowable_enctypes which is located in libgss_glue.
The libgssglue uses gss_union_cred_t structure.

This happens in limit_krb5_enctypes() in krb5_util.c

Unfortunately, gss_union_cred_t in libgssglue is missing one (first) item
compared to libgssapi_krb5.so.2, thus count is stored instead of mechs_arra=
y.
The mechs_array contains value 1 as I have shown. Dereferrencing means
segfault. =


Btw, do you have HAVE_SET_ALLOWABLE_ENCTYPES ?

-- =

Luk=E1=B9 Hejtm=E1nek

  reply	other threads:[~2010-03-09 15:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-18 14:27 ANNOUNCE: nfs-utils-1.2.2 released Steve Dickson
     [not found] ` <20100304201941.GL19154@ics.muni.cz>
     [not found]   ` <4B9021EF.60309@oracle.com>
     [not found]     ` <20100304212149.GM19154@ics.muni.cz>
2010-03-04 22:30       ` Chuck Lever
2010-03-04 22:40         ` Lukas Hejtmanek
2010-03-08 10:16           ` Lukas Hejtmanek
2010-03-08 12:02             ` Jeff Layton
2010-03-08 12:11               ` Lukas Hejtmanek
2010-03-08 13:44                 ` Kevin Coffman
2010-03-08 15:30                   ` Lukas Hejtmanek
2010-03-08 19:21                     ` Kevin Coffman
2010-03-08 19:40                       ` Lukas Hejtmanek
2010-03-08 19:48                         ` Jeff Layton
     [not found]                           ` <20100308144825.0e1afa59-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-03-09 10:35                             ` Lukas Hejtmanek
2010-03-09 15:18                               ` Kevin Coffman
2010-03-09 15:53                                 ` Lukas Hejtmanek [this message]
2010-03-09 17:04                                   ` Kevin Coffman
2010-03-09 17:29                                     ` Lukas Hejtmanek
2010-03-09 17:41                                       ` Lukas Hejtmanek
2010-03-09 18:26                                         ` Kevin Coffman
2010-03-09 18:52                                           ` Lukas Hejtmanek
2010-03-08 19:48                         ` Kevin Coffman
2010-03-08 17:42                   ` Steve Dickson

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=20100309155310.GR19154@ics.muni.cz \
    --to=xhejtman@ics.muni.cz \
    --cc=jlayton@redhat.com \
    --cc=kwc@citi.umich.edu \
    --cc=linux-nfs@vger.kernel.org \
    --cc=nfsv4@linux-nfs.org \
    /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