From: Andrew Price <anprice@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [ClusterLabs] gfs2-utils 3.3.0 released
Date: Tue, 8 Sep 2020 13:20:55 +0100 [thread overview]
Message-ID: <e9e91d5d-d810-6c88-b19e-3edf45d4d493@redhat.com> (raw)
In-Reply-To: <20200907212201.GS8773@valentin-vidic.from.hr>
On 07/09/2020 22:22, Valentin Vidic wrote:
> On Mon, Sep 07, 2020 at 02:00:41PM +0100, Andrew Price wrote:
>> It should be consistent if it's the same alignment issue, I think. Perhaps
>> the build machines are different flavours of arm?
>
> That is possible, second build was scheduled on a different machine.
>
>> Could you give this one a try:
>>
>> https://pagure.io/gfs2-utils/c/eb102019?branch=andyp-restore-init-align
>
> Thanks, tests look good again on sparc64 with this patch applied:
>
> gfs2_edit tests
>
> 31: Save/restoremeta, defaults ok
> 32: Save/restoremeta, no compression ok
> 33: Save/restoremeta, min. block size ok
> 34: Save/restoremeta, 4 journals ok
> 35: Save/restoremeta, min. block size, 4 journals ok
> 36: Save metadata to /dev/null ok
>
Thanks for testing. I've pushed the patch to master.
Thinking about all the other cast-align warnings, we might be able to
replace many of our be*_to_cpu() calls with functions that take a char*
instead of integer types, so that we never have to cast char* to
uint{16,32,64}_t* and widen the alignment when reading the on-disk
structures. That should tidy up a lot of code too as we wouldn't need
intermediate pointers. I'll look into it.
Andy
prev parent reply other threads:[~2020-09-08 12:20 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
2020-09-07 21:22 ` Valentin Vidic
2020-09-08 12:20 ` Andrew Price [this message]
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=e9e91d5d-d810-6c88-b19e-3edf45d4d493@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).