From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Price Date: Mon, 7 Sep 2020 14:00:41 +0100 Subject: [Cluster-devel] [ClusterLabs] gfs2-utils 3.3.0 released In-Reply-To: <20200904174205.GQ8773@valentin-vidic.from.hr> References: <20200903223932.GK8773@valentin-vidic.from.hr> <06377e85-04f1-d828-9e75-d81629fcd59c@redhat.com> <20200904061827.GL8773@valentin-vidic.from.hr> <20200904174205.GQ8773@valentin-vidic.from.hr> Message-ID: <077d4fb3-5642-f050-f68c-fb23964c3e02@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 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