From: Cyril Hrubis <chrubis@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: Linux Test Project <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v10 3/3] coredump02: Verify ELF structure and notes
Date: Thu, 10 Sep 2026 15:02:50 +0200 [thread overview]
Message-ID: <aqKqev1nXfieuJK4@yuki.lan> (raw)
In-Reply-To: <6aa2aa04.c9eda3e9.76660.270b@mx.google.com>
Hi!
> > AFAIK the 4 byte padding may happen on x86_64 only for a historical
> > reasons and x86_64 is at the same time capable of handling unaligned
> > access. AArch64 should have 8 byte padding.
>
> yes, it happens only in x86_64, but I wouldn't rely too much on unaligned
> access handling if it's just few bytes copy away. code is 100% stable like
> this.
It looks like working around potentional bugs rather than anything else.
The elements should be aligned so that they could be accessed on the
targed architecture.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-09-10 13:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 12:07 [LTP] [PATCH v10 0/3] coredump testing suite Andrea Cervesato
2026-09-09 12:07 ` [LTP] [PATCH v10 1/3] lib: Add SAFE_FILE_VPRINTF() Andrea Cervesato
2026-09-09 13:40 ` [LTP] " linuxtestproject.agent
2026-09-09 12:07 ` [LTP] [PATCH v10 2/3] coredump01: New core_pattern specifiers test Andrea Cervesato
2026-09-09 12:07 ` [LTP] [PATCH v10 3/3] coredump02: Verify ELF structure and notes Andrea Cervesato
2026-09-10 10:21 ` Cyril Hrubis
2026-09-10 11:14 ` Andrea Cervesato via ltp
2026-09-10 12:47 ` Cyril Hrubis
2026-09-10 13:00 ` Andrea Cervesato via ltp
2026-09-10 13:02 ` Cyril Hrubis [this message]
2026-09-10 13:26 ` Andrea Cervesato via ltp
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=aqKqev1nXfieuJK4@yuki.lan \
--to=chrubis@suse.cz \
--cc=andrea.cervesato@suse.com \
--cc=ltp@lists.linux.it \
/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