From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Price Date: Wed, 15 Mar 2017 11:24:39 +0000 Subject: [Cluster-devel] [PATCH] gfs2: Avoid alignment hole in struct lm_lockname In-Reply-To: <1110213219.31149233.1488824878103.JavaMail.zimbra@redhat.com> References: <1488810836-11427-1-git-send-email-agruenba@redhat.com> <1110213219.31149233.1488824878103.JavaMail.zimbra@redhat.com> Message-ID: <9193e110-2a56-8ab8-ffef-c2506be6e596@redhat.com> List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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 > | CC: #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