cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS2: Pull request (merge window) addendum
Date: Thu, 23 Feb 2017 10:37:43 -0500 (EST)	[thread overview]
Message-ID: <1248726520.26059207.1487864263447.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <414247014.26059064.1487864206659.JavaMail.zimbra@redhat.com>

Hi Linus,

Please consider pulling the following additional patch for the GFS2 file system.

Sorry for the lack of bake time on this one, but it is high priority, simple, and has been well tested.

Bob Peterson

----------------------------------------------------------------
The following changes since commit c548a1c175608e268f6495f3f82461303584d1c9:

  gfs2: Make gfs2_write_full_page static (2017-02-03 08:23:47 -0500)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git tags/gfs2-4.11.addendum

for you to fetch changes up to f38e5fb95a1f8feda88531eedc98f69b24748712:

  gfs2: Add missing rcu locking for glock	lookup (2017-02-23 10:06:00 -0500)

----------------------------------------------------------------
This is an addendum for the 4.11 merge window.

Andy Price wrote this patch to close a nasty race condition
that allows access to glocks that are being destroyed. Without
this patch, GFS2 is vulnerable to random corruption and kernel
panic.

----------------------------------------------------------------
Andrew Price (1):
      gfs2: Add missing rcu locking for glock	lookup

 fs/gfs2/glock.c | 5 +++++
 1 file changed, 5 insertions(+)



       reply	other threads:[~2017-02-23 15:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <414247014.26059064.1487864206659.JavaMail.zimbra@redhat.com>
2017-02-23 15:37 ` Bob Peterson [this message]
     [not found] <345457636.29256639.1499454960354.JavaMail.zimbra@redhat.com>
2017-07-07 19:17 ` [Cluster-devel] GFS2: Pull request (merge window) addendum Bob Peterson

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=1248726520.26059207.1487864263447.JavaMail.zimbra@redhat.com \
    --to=rpeterso@redhat.com \
    /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).