All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Christoph Hellwig <hch@lst.de>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfsd: don't get write access twіce in nfsd_setattr
Date: Thu, 9 Feb 2017 16:46:05 +0100	[thread overview]
Message-ID: <20170209154605.GA16292@lst.de> (raw)
In-Reply-To: <20170209154307.GD17622@fieldses.org>

On Thu, Feb 09, 2017 at 10:43:07AM -0500, J. Bruce Fields wrote:
> On Thu, Feb 09, 2017 at 02:25:16PM +0100, Christoph Hellwig wrote:
> > On Wed, Feb 08, 2017 at 04:51:01PM -0500, J. Bruce Fields wrote:
> > > > FYI, Chuck just reported another issue, let's wait for that for now.
> > 
> > I can't really reproduce the issue Chuck reported.  So let's get this
> > fixup in for now, especially as Linus replied to the thread it was
> > reported in and asked for it.
> 
> I can't find that reply--am I missing a thread?

Dave reported it in reply to Linus' 4.10-rc7 announcement.
Looks like neither you nor linux-nfs were Cc'ed on that.

> OK, so for 4.10 I have:
> 
> 	nfsd: don't get write access twice in nfsd_setattr
> 	nfsd: restore owner override for truncate

Yepp.  Sorry for the mess.

      reply	other threads:[~2017-02-09 15:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-07  9:12 [PATCH] nfsd: don't get write access twіce in nfsd_setattr Christoph Hellwig
2017-02-08 21:45 ` J. Bruce Fields
2017-02-08 21:50   ` Christoph Hellwig
2017-02-08 21:51     ` J. Bruce Fields
2017-02-09 13:25       ` Christoph Hellwig
2017-02-09 15:43         ` J. Bruce Fields
2017-02-09 15:46           ` Christoph Hellwig [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=20170209154605.GA16292@lst.de \
    --to=hch@lst.de \
    --cc=bfields@fieldses.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 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.