All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS2: pull request for high-priority bug
Date: Wed, 15 Mar 2017 10:32:38 -0400 (EDT)	[thread overview]
Message-ID: <1400281796.2601400.1489588358478.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <186538212.2600624.1489588290616.JavaMail.zimbra@redhat.com>

Hi Linus,

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

Regards,

Bob Peterson

----------------------------------------------------------------
The following changes since commit ae50dfd61665086e617cc9e554a1285d52765670:

  Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2017-03-14 21:31:23 -0700)

are available in the git repository at:

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

for you to fetch changes up to 28ea06c46fbcab63fd9a55531387b7928a18a590:

  gfs2: Avoid alignment hole in struct lm_lockname (2017-03-15 10:06:07 -0400)

----------------------------------------------------------------
This is an emergency patch for 4.11-rc3

The GFS2 developers uncovered a really nasty problem that
can lead to random corruption and kernel panic, much like
the last one. Andreas Gruenbacher wrote this simple one-line
patch to fix the problem:

28ea06c gfs2: Avoid alignment hole in struct lm_lockname

----------------------------------------------------------------
Andreas Gruenbacher (1):
      gfs2: Avoid alignment hole in struct lm_lockname

 fs/gfs2/incore.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)



WARNING: multiple messages have this Message-ID (diff)
From: Bob Peterson <rpeterso@redhat.com>
To: torvalds@linux-foundation.org
Cc: cluster-devel <cluster-devel@redhat.com>, linux-kernel@vger.kernel.org
Subject: GFS2: pull request for high-priority bug
Date: Wed, 15 Mar 2017 10:32:38 -0400 (EDT)	[thread overview]
Message-ID: <1400281796.2601400.1489588358478.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <186538212.2600624.1489588290616.JavaMail.zimbra@redhat.com>

Hi Linus,

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

Regards,

Bob Peterson

----------------------------------------------------------------
The following changes since commit ae50dfd61665086e617cc9e554a1285d52765670:

  Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2017-03-14 21:31:23 -0700)

are available in the git repository at:

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

for you to fetch changes up to 28ea06c46fbcab63fd9a55531387b7928a18a590:

  gfs2: Avoid alignment hole in struct lm_lockname (2017-03-15 10:06:07 -0400)

----------------------------------------------------------------
This is an emergency patch for 4.11-rc3

The GFS2 developers uncovered a really nasty problem that
can lead to random corruption and kernel panic, much like
the last one. Andreas Gruenbacher wrote this simple one-line
patch to fix the problem:

28ea06c gfs2: Avoid alignment hole in struct lm_lockname

----------------------------------------------------------------
Andreas Gruenbacher (1):
      gfs2: Avoid alignment hole in struct lm_lockname

 fs/gfs2/incore.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

       reply	other threads:[~2017-03-15 14:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <186538212.2600624.1489588290616.JavaMail.zimbra@redhat.com>
2017-03-15 14:32 ` Bob Peterson [this message]
2017-03-15 14:32   ` GFS2: pull request for high-priority bug Bob Peterson
2017-03-15 17:21   ` [Cluster-devel] " Linus Torvalds
2017-03-15 17:21     ` Linus Torvalds
2017-03-15 17:40     ` [Cluster-devel] " Bob Peterson
2017-03-15 17:40       ` 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=1400281796.2601400.1489588358478.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 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.