All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Valites <mvalites@buffalo.edu>
To: linux-nfs@vger.kernel.org
Subject: Re: RH 7 nfs-utils update causes segfault
Date: Tue, 08 Mar 2016 15:27:13 -0500	[thread overview]
Message-ID: <56DF35A1.1000007@buffalo.edu> (raw)
In-Reply-To: <alpine.OSX.2.19.9992.1603081513100.78938@planck.local>

On 03/08/2016 03:16 PM, Benjamin Coddington wrote:

> That's where we want the backtrace; that's when you should do 'bt'.  Feel
> free to leave out everything else.

Wow - Sorry about that.

(gdb) handle SIG37 nostop
Signal        Stop      Print   Pass to program Description
SIG37         No        Yes     Yes             Real-time event 37
(gdb) continue
Continuing.

Program received signal SIG37, Real-time event 37.

Program received signal SIG37, Real-time event 37.

Program received signal SIG37, Real-time event 37.

Program received signal SIG37, Real-time event 37.

Program received signal SIG37, Real-time event 37.

Program received signal SIGSEGV, Segmentation fault.
__strcmp_ssse3 () at ../sysdeps/x86_64/strcmp.S:212
212             movlpd  (%rdi), %xmm1
(gdb) bt
#0  __strcmp_ssse3 () at ../sysdeps/x86_64/strcmp.S:212
#1  0x00007fec0dfb60f4 in find_keytab_entry (context=0x7fec0f82d6d0, 
kt=0x7fec0f829a10, tgtname=tgtname@entry=0x7fec0f829910 
"ubfs1.itorg.ad.buffalo.edu",
     kte=kte@entry=0x7fffc8ca1ec0, 
svcnames=svcnames@entry=0x7fffc8ca1e90) at krb5_util.c:894
#2  0x00007fec0dfb6ded in gssd_refresh_krb5_machine_credential 
(hostname=0x7fec0f829910 "ubfs1.itorg.ad.buffalo.edu", 
ple=ple@entry=0x0, service=service@entry=0x0)
     at krb5_util.c:1311
#3  0x00007fec0dfb4030 in krb5_use_machine_creds 
(clp=clp@entry=0x7fec0f82bcb0, uid=uid@entry=0, 
tgtname=tgtname@entry=0x0, service=service@entry=0x0,
     rpc_clnt=rpc_clnt@entry=0x7fffc8ca2000) at gssd_proc.c:1086
#4  0x00007fec0dfb4416 in process_krb5_upcall 
(clp=clp@entry=0x7fec0f82bcb0, uid=0, fd=13, tgtname=tgtname@entry=0x0, 
service=service@entry=0x0) at gssd_proc.c:1222
#5  0x00007fec0dfb4d03 in handle_gssd_upcall 
(clp=clp@entry=0x7fec0f82bcb0) at gssd_proc.c:1413
#6  0x00007fec0dfb264e in scan_poll_results (ret=1) at gssd_main_loop.c:85
#7  gssd_poll (nfds=<optimized out>, fds=<optimized out>) at 
gssd_main_loop.c:201
#8  gssd_run () at gssd_main_loop.c:258
#9  0x00007fec0dfb111a in main (argc=<optimized out>, 
argv=0x7fffc8ca2418) at gssd.c:216
(gdb) continue
Continuing.

Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
(gdb)

FWIW, the ubfs1.itorg.ad.buffalo.edu hostname mentioned in the backtrace 
is the nfs server.

  reply	other threads:[~2016-03-08 20:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-07 15:48 RH 7 nfs-utils update causes Mark Valites
2016-03-07 16:00 ` Benjamin Coddington
2016-03-07 16:27   ` RH 7 nfs-utils update causes segfault Mark Valites
2016-03-07 19:49     ` Benjamin Coddington
2016-03-08 16:57       ` Mark Valites
2016-03-08 18:21         ` Benjamin Coddington
2016-03-08 18:39           ` Mark Valites
2016-03-08 19:07             ` Benjamin Coddington
2016-03-08 19:30               ` Mark Valites
2016-03-08 20:16                 ` Benjamin Coddington
2016-03-08 20:27                   ` Mark Valites [this message]
2016-03-08 20:37                     ` Benjamin Coddington
2016-03-08 20:51                       ` Mark Valites

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=56DF35A1.1000007@buffalo.edu \
    --to=mvalites@buffalo.edu \
    --cc=linux-nfs@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.