From: Andrew Price <anprice@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [ClusterLabs] gfs2-utils 3.3.0 released
Date: Mon, 7 Sep 2020 14:00:41 +0100 [thread overview]
Message-ID: <077d4fb3-5642-f050-f68c-fb23964c3e02@redhat.com> (raw)
In-Reply-To: <20200904174205.GQ8773@valentin-vidic.from.hr>
On 04/09/2020 18:42, Valentin Vidic wrote:
> On Fri, Sep 04, 2020 at 02:42:10PM +0100, Andrew Price wrote:
>> I'm pretty sure I know which change added the bug, but my Debian sparc64 vm
>> is hitting this problem too frequently to test:
>>
>> https://lkml.org/lkml/2020/5/18/1455
>>
>> So probably the best I can do is build with -Wcast-align=strict and make the
>> relevant warning go away.
>
> I tried to reproduce the problem on arm, but after a rebuild tests look
> fine, so I'm not sure anymore if this is a new problem or something that
> happens randomly.
It should be consistent if it's the same alignment issue, I think.
Perhaps the build machines are different flavours of arm?
> For sparc64 it seems to be reproducible and I have access to a machine
> in case you want me to test some patches.
Could you give this one a try:
https://pagure.io/gfs2-utils/c/eb102019?branch=andyp-restore-init-align
Andy
next prev parent reply other threads:[~2020-09-07 13:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 15:41 [Cluster-devel] gfs2-utils 3.3.0 released Andrew Price
2020-09-03 22:39 ` [Cluster-devel] [ClusterLabs] " Valentin Vidić
2020-09-04 3:13 ` Andrew Price
2020-09-04 6:18 ` Valentin Vidic
2020-09-04 13:42 ` Andrew Price
2020-09-04 17:42 ` Valentin Vidic
2020-09-07 13:00 ` Andrew Price [this message]
2020-09-07 21:22 ` Valentin Vidic
2020-09-08 12:20 ` Andrew Price
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=077d4fb3-5642-f050-f68c-fb23964c3e02@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).