public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Lukas Hejtmanek <xhejtman@ics.muni.cz>
To: Jeff Layton <jlayton@redhat.com>
Cc: Kevin Coffman <kwc@citi.umich.edu>,
	NFSv3 list <linux-nfs@vger.kernel.org>,
	nfsv4@linux-nfs.org
Subject: Re: ANNOUNCE: nfs-utils-1.2.2 released.
Date: Tue, 9 Mar 2010 11:35:48 +0100	[thread overview]
Message-ID: <20100309103548.GJ19154@ics.muni.cz> (raw)
In-Reply-To: <20100308144825.0e1afa59-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>

On Mon, Mar 08, 2010 at 02:48:25PM -0500, Jeff Layton wrote:
> What would probably help some is to do a bit more analysis with gdb.
> Maybe see if you can determine where it's falling down in libgssglue
> and why. That may help us to determine what the actual problem is.

using gdb and debug in libgssglue, it looks like there is a mess in
structures:
Core was generated by `/tmp/nfs-utils-1.2.2/utils/gssd/gssd -vvv'.
Program terminated with signal 11, Segmentation fault.
#0  0x00007f8a77c0a5ef in __gss_get_mechanism_cred (union_cred=3D0x1be3=
a00,
mech_type=3D0x6114f0) at g_glue.c:295
295             if (g_OID_equal(mech_type, &union_cred->mechs_array[i])=
)
(gdb) print *union_cred
$1 =3D {count =3D 29243904, mechs_array =3D 0x1, cred_array =3D 0x1be8b=
e0, auxinfo
=3D {name =3D {length =3D 29264896, value =3D 0x11},=20
    name_type =3D 0x1be8bc0, creation_time =3D 140232705185984, time_re=
c
=3D 1268127776, cred_usage =3D 86400}}

this seems to be because gss_acquire_cred is defined in both libgssglue=
=2Eso and
libgssapi_krb5.so

and these two libs do not agree on gss_union_cred_t:

libgssapi_krb5:
typedef struct gss_cred_id_struct {
        struct gss_cred_id_struct *loopback;
        int                     count;
        gss_OID                 mechs_array;
        gss_cred_id_t           *cred_array;
        gss_union_cred_auxinfo  auxinfo;
} gss_union_cred_desc, *gss_union_cred_t;

libgssglu:
typedef struct gss_union_cred_t {
        int                     count;
        gss_OID                 mechs_array;
        gss_cred_id_t *         cred_array;
        gss_union_cred_auxinfo  auxinfo;
} gss_union_cred_desc, *gss_union_cred_t;


--=20
Luk=E1=B9 Hejtm=E1nek

  parent reply	other threads:[~2010-03-09 10:35 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 [this message]
2010-03-09 15:18                               ` Kevin Coffman
2010-03-09 15:53                                 ` Lukas Hejtmanek
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=20100309103548.GJ19154@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