public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Lukas Hejtmanek <xhejtman@ics.muni.cz>
To: Chuck Lever <chuck.lever@oracle.com>
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: Mon, 8 Mar 2010 11:16:07 +0100	[thread overview]
Message-ID: <20100308101607.GR19154@ics.muni.cz> (raw)
In-Reply-To: <20100304224011.GN19154@ics.muni.cz>

Hello,

it appears that gssd fails to run with nfs-utils-1.2.2.

It is terminated by signal SIGSEGV.

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff70a3ace in ?? () from /usr/lib/libgssglue.so.1
(gdb) where
#0  0x00007ffff70a3ace in ?? () from /usr/lib/libgssglue.so.1
#1  0x00007ffff70a6781 in gss_set_allowable_enctypes ()
   from /usr/lib/libgssglue.so.1
#2  0x0000000000408793 in limit_krb5_enctypes (sec=3D0x7fffffffddf0, uid=3D=
0)
    at krb5_util.c:336
#3  0x0000000000407215 in create_auth_rpc_client (clp=3D0x617c10, =

    clnt_return=3D0x7fffffffe2f0, auth_return=3D0x7fffffffe2e8, uid=3D0, au=
thtype=3D0)
    at gssd_proc.c:801
#4  0x0000000000407896 in process_krb5_upcall (clp=3D0x617c10, uid=3D0, fd=
=3D13, =

    tgtname=3D0x0, service=3D0x0) at gssd_proc.c:978
#5  0x0000000000408052 in handle_gssd_upcall (clp=3D0x617c10) at
gssd_proc.c:1215
#6  0x0000000000404e21 in scan_poll_results (ret=3D1) at gssd_main_loop.c:82
#7  0x0000000000405442 in gssd_run () at gssd_main_loop.c:230
#8  0x0000000000404d47 in main (argc=3D2, argv=3D0x7fffffffe638) at gssd.c:=
187


-- =

Luk=E1=B9 Hejtm=E1nek

  reply	other threads:[~2010-03-08 10:16 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 [this message]
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
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=20100308101607.GR19154@ics.muni.cz \
    --to=xhejtman@ics.muni.cz \
    --cc=chuck.lever@oracle.com \
    --cc=jlayton@redhat.com \
    --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