linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tom Boven <tom.boven@telenet.be>
To: Kevin Coffman <kwc@citi.umich.edu>
Cc: linux-nfs@vger.kernel.org, 619052@bugs.debian.org,
	Bones <bones_was_here@yahoo.com.au>, "Luk Claes" <luk@debian.org>,
	"Aníbal Monsalve Salazar" <anibal@debian.org>
Subject: Re: rpc.gssd: double free or corruption
Date: Wed, 23 Mar 2011 19:04:24 +0100	[thread overview]
Message-ID: <4D8A3628.9040506@telenet.be> (raw)
In-Reply-To: <AANLkTimX=F3gk2_optA5pX315vpPARuP0DsgmBy0YXbO@mail.gmail.com>

Op 23-03-11 16:32, Kevin Coffman schreef:
> 2011/3/22 Aníbal Monsalve Salazar<anibal@debian.org>:
>    
>> On Wed, Mar 16, 2011 at 09:28:04PM -0400, Kevin Coffman wrote:
>>      
>>> A new version of library libgssglue is now available from:
>>>
>>> http://www.citi.umich.edu/projects/nfsv4/linux/libgssglue/libgssglue-0.2.tar.gz
>>>
>>> Changes since libgssglue-0.1:
>>>
>>>        * Modify the gss_acquire_cred() code to accept, and
>>>          properly handle, an input name of GSS_C_NO_NAME.
>>>          Other misc. changes to support this change.
>>>        * Remove some generated files from git.  Change
>>>          autogen.sh to clean up files that might become
>>>          outdated and incompatible.
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>        
>> Hello Kevin,
>>
>> Please have a look at Debian bug#619052.
>>
>> http://bugs.debian.org/619052
>>
>> The attached file is the original bug report.
>>
>> Thank you,
>>
>> Aníbal
>>      
> Hi,
> So far, I'm stumped.  I've been unable to reproduce this on my Fedora
> 13 machine.  I have a slightly different version of libc, an earlier
> version of kerberos, and a later version of nfs-utils (the pnfs
> version).  I went back to stock versions of everything and simply
> replaced libgssglue with the new version.
>
> glibc-2.12.2-1.x86_64
> krb5-libs-1.7.1-17.fc13.x86_64
> krb5-debuginfo-1.7.1-17.fc13.x86_64
> krb5-auth-dialog-0.15-1.fc13.x86_64
> krb5-workstation-1.7.1-17.fc13.x86_64
> pam_krb5-2.3.11-1.fc13.x86_64
> krb5-devel-1.7.1-17.fc13.x86_64
> nfs-utils-lib-devel-1.1.5-1.fc13.x86_64
> nfs-utils-1.2.3-2.pnfs.fc15.x86_64
> nfs-utils-lib-1.1.5-1.fc13.x86_64
> nfs-utils-lib-debuginfo-1.1.5-1.fc13.x86_64
>
> Are you using any special options to gssd?
>
> K.C.
>
>    
I've just checked but no, I don't use any option at all to start rpc.gssd

Tom


      reply	other threads:[~2011-03-23 18:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-17  1:28 libgssglue-0.2 Kevin Coffman
2011-03-23  0:09 ` rpc.gssd: double free or corruption (was: libgssglue-0.2) Aníbal Monsalve Salazar
     [not found]   ` <20110323000925.GA6353-q3oZDYqQg6zyUObV3Cmqeti2O/JbrIOy@public.gmane.org>
2011-03-23  3:57     ` Kevin Coffman
2011-03-23 15:32   ` Kevin Coffman
2011-03-23 18:04     ` Tom Boven [this message]

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=4D8A3628.9040506@telenet.be \
    --to=tom.boven@telenet.be \
    --cc=619052@bugs.debian.org \
    --cc=anibal@debian.org \
    --cc=bones_was_here@yahoo.com.au \
    --cc=kwc@citi.umich.edu \
    --cc=linux-nfs@vger.kernel.org \
    --cc=luk@debian.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;
as well as URLs for NNTP newsgroup(s).