linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: bfields@redhat.com
Cc: jlayton@poochiereds.net,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	linux-nfs@vger.kernel.org
Subject: NFS: SECINFO: security flavor 390003 is not supported
Date: Wed, 4 Jan 2017 14:03:27 -0500	[thread overview]
Message-ID: <20170104190327.v3wbpcbqtfa5jy7d@codemonkey.org.uk> (raw)

Since upgrading to 4.10-rc2, my nfs server has started printing these..

[  161.668635] NFS: SECINFO: security flavor 390003 is not supported
[  161.668655] NFS: SECINFO: security flavor 390004 is not supported
[  161.668670] NFS: SECINFO: security flavor 390005 is not supported

Client is debian's 4.8 kernel with default mount options, so sec=sys

What should I be doing to suppress these ? What causes them ?

	Dave


             reply	other threads:[~2017-01-04 19:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04 19:03 Dave Jones [this message]
2017-01-04 19:23 ` NFS: SECINFO: security flavor 390003 is not supported Steve Dickson
2017-01-04 19:29   ` Dave Jones
2017-01-04 19:48     ` J. Bruce Fields

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=20170104190327.v3wbpcbqtfa5jy7d@codemonkey.org.uk \
    --to=davej@codemonkey.org.uk \
    --cc=bfields@redhat.com \
    --cc=jlayton@poochiereds.net \
    --cc=linux-kernel@vger.kernel.org \
    --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).