linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J . Bruce Fields" <bfields@fieldses.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	Jeff Layton <jlayton@kernel.org>,
	Eddie Horng <eddiehorng.tw@gmail.com>,
	overlayfs <linux-unionfs@vger.kernel.org>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] nfsd: fix leaked file lock with nfs exported overlayfs
Date: Wed, 1 Aug 2018 07:40:19 -0400	[thread overview]
Message-ID: <20180801114019.GA15798@fieldses.org> (raw)
In-Reply-To: <CAOQ4uxg+kuAuZ=o7U+77mrYO5zkFAGCkNpiZSVDdYKcdm631_w@mail.gmail.com>

On Wed, Aug 01, 2018 at 09:18:24AM +0300, Amir Goldstein wrote:
> On Tue, Jul 17, 2018 at 5:24 PM, Miklos Szeredi <miklos@szeredi.hu> wrote:
> > Needs a Cc: stable@... tag then.
> >
> > Should I take this patch (based on the fact that it only affects
> > overlayfs exports)?
> >
> > Or will you take it, Bruce?
> >
> 
> Bruce? Jeff?
> 
> It's probably a good time for someone to put this patch in -next.
> 
> Should Miklos do it?

I'm applying it, thanks for the reminder.  (Or I'd be OK with Miklos
taking it.)

--b.

      reply	other threads:[~2018-08-01 13:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-13 14:22 [PATCH] nfsd: fix leaked file lock with nfs exported overlayfs Amir Goldstein
2018-07-13 15:40 ` Jeff Layton
2018-07-13 16:05   ` Amir Goldstein
2018-07-17 14:24     ` Miklos Szeredi
2018-08-01  6:18       ` Amir Goldstein
2018-08-01 11:40         ` J . Bruce Fields [this message]

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=20180801114019.GA15798@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=amir73il@gmail.com \
    --cc=eddiehorng.tw@gmail.com \
    --cc=jlayton@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /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).