linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel mailing list <linux-kernel@vger.kernel.org>,
	Linux NFS mailing list <linux-nfs@vger.kernel.org>
Subject: [GIT PULL] Please pull 1 bugfix for the NFS client
Date: Sun, 29 Jan 2012 22:14:58 +0000	[thread overview]
Message-ID: <1327875297.6246.1.camel@lade.trondhjem.org> (raw)

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

Hi Linus,

Please pull from the signed tag "nfs-for-3.3-3" in the repository at

   git pull git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tag nfs-for-3.3-3

This will update the following files through the appended changesets.

  Cheers,
    Trond

----
 net/sunrpc/auth_generic.c |   17 ++++++++++++++++-
 1 files changed, 16 insertions(+), 1 deletions(-)

commit 875ad3f8e7dff6bc1d053e5bfe73d8e8d2e6ae67
Author: Trond Myklebust <Trond.Myklebust@netapp.com>
Date:   Mon Jan 23 12:49:36 2012 -0500

    SUNRPC: Fix machine creds in generic_create_cred and generic_match
    
    - generic_create_cred needs to copy the '.principal' field.
    - generic_match needs to ignore the groups and match on the '.principal'
      field.
    
    This fixes an Oops that was introduced by commit 68c9715 (SUNRPC:
    Clean up the RPCSEC_GSS service ticket requests)
    
    Reported-by: J. Bruce Fields <bfields@redhat.com>
    Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
    Tested-by: J. Bruce Fields <bfields@redhat.com>


-- 
Trond Myklebust
Linux NFS client maintainer

NetApp
Trond.Myklebust@netapp.com
www.netapp.com


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

                 reply	other threads:[~2012-01-29 22:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1327875297.6246.1.camel@lade.trondhjem.org \
    --to=trond.myklebust@netapp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).