All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: stable@vger.kernel.org, Rik Theys <Rik.Theys@esat.kuleuven.be>,
	Trond Myklebust <Trond.Myklebust@netapp.com>,
	linux-nfs@vger.kernel.org, David Flyn <davidf@rd.bbc.co.uk>,
	Jeff Layton <jlayton@redhat.com>,
	659111@bugs.debian.org
Subject: Re: [PATCH 3.0.y, 3.2.y] NFSv4: Revalidate uid/gid after open
Date: Sat, 12 May 2012 10:20:14 +0100	[thread overview]
Message-ID: <1336814414.8274.501.camel@deadeye> (raw)
In-Reply-To: <20120511092020.GD5733@burratino>

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

On Fri, 2012-05-11 at 04:20 -0500, Jonathan Nieder wrote:
> This is a shorter (and more appropriate for stable kernels) analog to
> the following upstream commit:
> 
> commit 6926afd1925a54a13684ebe05987868890665e2b
> Author: Trond Myklebust <Trond.Myklebust@netapp.com>
> Date:   Sat Jan 7 13:22:46 2012 -0500
> 
>     NFSv4: Save the owner/group name string when doing open
[...]

Added to the queue for 3.2.y, thanks.

Ben.

-- 
Ben Hutchings
Experience is directly proportional to the value of equipment destroyed.
                                                         - Carolyn Scheppner

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

  reply	other threads:[~2012-05-12  9:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.LRH.2.00.1204242156380.28096@helium.esat.kuleuven.be>
2012-05-11  9:20 ` [PATCH 3.0.y, 3.2.y] NFSv4: Revalidate uid/gid after open Jonathan Nieder
2012-05-12  9:20   ` Ben Hutchings [this message]
2012-05-12 19:13     ` Jonathan Nieder
2012-05-18 19:31   ` Greg KH

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=1336814414.8274.501.camel@deadeye \
    --to=ben@decadent.org.uk \
    --cc=659111@bugs.debian.org \
    --cc=Rik.Theys@esat.kuleuven.be \
    --cc=Trond.Myklebust@netapp.com \
    --cc=davidf@rd.bbc.co.uk \
    --cc=jlayton@redhat.com \
    --cc=jrnieder@gmail.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.