From: Andrew Price <anprice@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] gfs2: Avoid alignment hole in struct lm_lockname
Date: Wed, 15 Mar 2017 11:24:39 +0000 [thread overview]
Message-ID: <9193e110-2a56-8ab8-ffef-c2506be6e596@redhat.com> (raw)
In-Reply-To: <1110213219.31149233.1488824878103.JavaMail.zimbra@redhat.com>
On 06/03/17 18:27, Bob Peterson wrote:
> ----- Original Message -----
> | Commit 88ffbf3e03 switches to using rhashtables for glocks, hashing over
> | the entire struct lm_lockname instead of its individual fields. On some
> | architectures, struct lm_lockname contains a hole of uninitialized
> | memory due to alignment rules, which now leads to incorrect hash values.
> | Get rid of that hole.
> |
> | Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
> | CC: <stable@vger.kernel.org> #v4.3+
> | ---
> Hi,
>
> Thanks. This is now applied to the for-next branch of the linux-gfs2 tree:
> https://git.kernel.org/cgit/linux/kernel/git/gfs2/linux-gfs2.git/commit/?h=for-next&id=415730e5de2361518a2d884c0f64de37c5bfefeb
Will this get sent to Linus in the 4.11 cycle or is it being held for
the 4.12 merge window?
Andy
next prev parent reply other threads:[~2017-03-15 11:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 14:33 [Cluster-devel] [PATCH] gfs2: Avoid alignment hole in struct lm_lockname Andreas Gruenbacher
2017-03-06 15:10 ` Bob Peterson
2017-03-06 15:15 ` Steven Whitehouse
2017-03-06 16:55 ` Andreas Gruenbacher
2017-03-06 17:43 ` Steven Whitehouse
2017-03-06 18:27 ` Bob Peterson
2017-03-15 11:24 ` Andrew Price [this message]
2017-03-15 11:41 ` Andreas Gruenbacher
2017-03-15 14:34 ` 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=9193e110-2a56-8ab8-ffef-c2506be6e596@redhat.com \
--to=anprice@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).