From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: "Cyril Hrubis" <chrubis@suse.cz>
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 13:00:51 +0000 [thread overview]
Message-ID: <6aa2aa04.c9eda3e9.76660.270b@mx.google.com> (raw)
In-Reply-To: <aqKmzG1kexhUuv1c@yuki.lan>
> 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.
--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-09-10 13:01 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 [this message]
2026-09-10 13:02 ` Cyril Hrubis
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=6aa2aa04.c9eda3e9.76660.270b@mx.google.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=chrubis@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.