linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Gerstner <matthias.gerstner@nefkom.net>
To: Steve Dickson <SteveD@RedHat.com>
Cc: linux-nfs@vger.kernel.org, Justin Mitchell <jumitche@redhat.com>
Subject: Re: nfs-utils: rpc.svcgssd segmentation fault in nss_gss_princ_to_ids()
Date: Thu, 22 Feb 2018 09:17:08 +0100	[thread overview]
Message-ID: <20180222081708.GA883@q910.gerrit.home> (raw)
In-Reply-To: <849cf544-ba0a-c218-020d-93f973ba7ab6@RedHat.com>

[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]

Hello,

thanks for your reply.

> It is... But in the future please in line your
> patch (which I have a the bottom of this reply)
> instead attaching it.. I just makes it easier 
> to review.

I will do so.

> Also note, at least with Fedora, we no longer use rpc.svcgssd
> instead we use gssproxy to access GSSAPI credentials

Okay. I have been running this NFS setup for years without touching much.
It looks like I should invest some time to check if everything is still up to
date.

> By moving this pragama statement both the no_strip 
> and reformat_group are also being exposed as 
> global variables in the libnfsidmap, correct?
> I'm not sure we want to do that, if that is the case.

I was not suggesting to accept this as a patch. I just wanted to make clear
what "helped" in my case.

I will try some more experiments when I have time. Maybe I can find a suitable
patch. Getter/Setter functions instead of the extern declared variables might
help.

Regards

Matthias

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-02-22  8:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-20 22:48 nfs-utils: rpc.svcgssd segmentation fault in nss_gss_princ_to_ids() Matthias Gerstner
2018-02-21 16:08 ` Steve Dickson
2018-02-22  8:17   ` Matthias Gerstner [this message]
2018-02-21 16:49 ` Justin Mitchell
2018-02-22  8:18   ` Matthias Gerstner
2018-02-22 23:10   ` matthias.gerstner

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=20180222081708.GA883@q910.gerrit.home \
    --to=matthias.gerstner@nefkom.net \
    --cc=SteveD@RedHat.com \
    --cc=jumitche@redhat.com \
    --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 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).