From: Simo Sorce <simo@redhat.com>
To: Linux NFS Mailing list <linux-nfs@vger.kernel.org>,
libtirpc-devel@lists.sourceforge.net
Cc: Steve Dickson <steved@redhat.com>
Subject: [PATCH 0/2] libtirpc and nfs-utils fix for export lucid context
Date: Fri, 5 Apr 2013 18:37:03 -0400 [thread overview]
Message-ID: <1365201425-21702-1-git-send-email-simo@redhat.com> (raw)
The following 2 patches go in tandem.
One is for libtirpc and the other for nfs-utils.
The standard gss_krb5_export_lucid_sec_context call actually deletes the gss context
after it has been exported, so these patches perform a complete hand over of the
context from libtirpc, so that the context handle can be nulled out in the
gss_krb5_export_lucid_sec_context and the code does not attempt to free it
twice and cause segmentation faults in the unlucky case.
Simo Sorce
next reply other threads:[~2013-04-05 22:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 22:37 Simo Sorce [this message]
2013-04-05 22:37 ` [PATCH 1/1] Fix private data giveaway Simo Sorce
2013-04-05 22:37 ` [PATCH 2/2] Fix double free when exporting lucid context Simo Sorce
2013-04-10 15:39 ` Steve Dickson
2013-04-10 15:39 ` [PATCH 1/1] Fix private data giveaway Steve Dickson
2013-04-09 19:41 ` [PATCH 0/2] libtirpc and nfs-utils fix for export lucid context Steve Dickson
2013-04-09 20:05 ` Simo Sorce
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=1365201425-21702-1-git-send-email-simo@redhat.com \
--to=simo@redhat.com \
--cc=libtirpc-devel@lists.sourceforge.net \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.com \
/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