All of lore.kernel.org
 help / color / mirror / Atom feed
From: bfields@fieldses.org (J. Bruce Fields)
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	Christoph Hellwig <hch@infradead.org>
Subject: [GIT] nfsd bugfix for 4.0
Date: Fri, 20 Mar 2015 12:21:47 -0400	[thread overview]
Message-ID: <20150320162147.GF2036@fieldses.org> (raw)

Please pull the following nfsd bugfix for 4.0:

  git://linux-nfs.org/~bfields/linux.git for-4.0

This is a fix for a crash easily triggered by 4.1 activity to a server
built with CONFIG_NFSD_PNFS.

There are some more bugfixes queued up that I intend to pass along next
week, but this is the most critical.

--b.

----------------------------------------------------------------
Christoph Hellwig (1):
      Subject: nfsd: don't recursively call nfsd4_cb_layout_fail

 fs/nfsd/nfs4layouts.c | 2 --
 1 file changed, 2 deletions(-)


             reply	other threads:[~2015-03-20 16:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-20 16:21 J. Bruce Fields [this message]
2015-03-20 16:24 ` [GIT] nfsd bugfix for 4.0 Christoph Hellwig
2015-03-20 16:41   ` J. Bruce Fields
2015-03-21 17:42     ` Linus Torvalds

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=20150320162147.GF2036@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=hch@infradead.org \
    --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 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.