All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: "J. R. Okajima" <hooanon05g@gmail.com>
Cc: "J. Bruce Fields" <bfields@redhat.com>,
	Jeff Layton <jlayton@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] NFSD, lost nfserrno() call in nfsd_setattr()
Date: Tue, 25 Mar 2014 16:41:50 -0400	[thread overview]
Message-ID: <20140325204149.GB30430@fieldses.org> (raw)
In-Reply-To: <6158.1395735542@jrobl>

On Tue, Mar 25, 2014 at 05:19:02PM +0900, J. R. Okajima wrote:
> 
> "J. Bruce Fields":
> > On Wed, Feb 19, 2014 at 12:27:53AM +0900, J. R. Okajima wrote:
> > > 
> > > There is a regression in
> > > 	208d0ac 2014-01-07 nfsd4: break only delegations when appropriate
> > > which deletes an nfserrno() call in nfsd_setattr() (by accident,
> > > probably), and NFSD becomes ignoring an error from VFS.
> > > 
> > > Here is a patch to fix it.
> >
> > Thanks for cathing that!  Queueing up for 3.14.
> 
> Now rc8 is released, but this patch is still un-merged.
> The bug is actually a show-stopper for my local tests.
> Do you really have a plan to do it? Or should I ask Linus Torvalds
> directly?

If you remember, just bug me once a week or so.  Snd then if it gets
this late, yes, sending straight to Linus with a cc: to the unresponsive
maintainer and any relevant mailing list is probably a reasonable thing
to do in this sort of situation.

Anyway, my screwup, apologies for not getting that merged at the start.

--b.

      reply	other threads:[~2014-03-25 20:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18 15:27 [PATCH] NFSD, lost nfserrno() call in nfsd_setattr() J. R. Okajima
2014-02-18 20:44 ` J. Bruce Fields
2014-03-25  8:19   ` J. R. Okajima
2014-03-25 20:41     ` 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=20140325204149.GB30430@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=bfields@redhat.com \
    --cc=hooanon05g@gmail.com \
    --cc=jlayton@redhat.com \
    --cc=linux-kernel@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.