From: Trond Myklebust <trondmy@hammerspace.com>
To: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Please pull another NFS client bugfix
Date: Thu, 16 Apr 2020 23:30:48 +0000 [thread overview]
Message-ID: <e2f62ab02037ca4ab2f72081851d3e0d0c521e77.camel@hammerspace.com> (raw)
In-Reply-To: <74a2fbfca03c6150c0a88e915109babbc45b9e08.camel@hammerspace.com>
On Thu, 2020-04-16 at 19:28 -0400, Trond Myklebust wrote:
> Hi Linus,
>
> The following changes since commit
> 8f3d9f354286745c751374f5f1fcafee6b3f3136:
>
> Linux 5.7-rc1 (2020-04-12 12:35:55 -0700)
>
> are available in the Git repository at:
>
> git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-
> for-5.7-3
>
> for you to fetch changes up to
> fbf4bcc9a8373122881909331f2f9566a128126e:
>
> NFS: Fix an ABBA spinlock issue in pnfs_update_layout() (2020-04-13
> 15:55:21 -0400)
>
> Thanks
> Trond
>
> ----------------------------------------------------------------
> NFS client bugfix for Linux 5.7
>
> Bugfix:
> - Fix an ABBA spinlock issue in pnfs_update_layout()
>
> ----------------------------------------------------------------
> Trond Myklebust (1):
> NFS: Fix an ABBA spinlock issue in pnfs_update_layout()
>
> fs/nfs/pnfs.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Sorry about the dup, Linus. I inadvertently hit 'send' before I had
added the usual Ccs...
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
parent reply other threads:[~2020-04-16 23:30 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <74a2fbfca03c6150c0a88e915109babbc45b9e08.camel@hammerspace.com>]
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=e2f62ab02037ca4ab2f72081851d3e0d0c521e77.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®