From: Vasily Gorbik <gor@linux.ibm.com>
To: "Shuah Khan" <shuah@kernel.org>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: Fangrui Song <i@maskray.me>, Xi Ruoyao <xry111@xry111.site>,
Heiko Carstens <hca@linux.ibm.com>,
Jens Remus <jremus@linux.ibm.com>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] selftests/vDSO: fix GNU hash table entry size for s390x
Date: Wed, 26 Feb 2025 20:37:59 +0100 [thread overview]
Message-ID: <your-ad-here.call-01740598679-ext-1013@work.hours> (raw)
In-Reply-To: <your-ad-here.call-01739836346-ext-7522@work.hours>
On Tue, Feb 18, 2025 at 12:52:31AM +0100, Vasily Gorbik wrote:
> On Mon, Feb 17, 2025 at 02:04:18PM +0100, Thomas Weißschuh wrote:
> > Commit 14be4e6f3522 ("selftests: vDSO: fix ELF hash table entry size for s390x")
> > changed the type of the ELF hash table entries to 64bit on s390x.
> > However the *GNU* hash tables entries are always 32bit.
> > The "bucket" pointer is shared between both hash algorithms.
> --
> > On s390x the GNU algorithm assigns and dereferences this pointer to a
> > 64bit value as a pointer to a 32bit value, leading to compiler warnings and
> > runtime crashes.
>
> I would rephrase it as follows:
>
> On s390, this caused the GNU hash algorithm to access its 32-bit entries as if they
> were 64-bit, triggering compiler warnings (assignment between "Elf64_Xword *" and
> "Elf64_Word *") and runtime crashes.
>
> And take it via s390 tree.
>
> Shuah, if you don't mind, may I get your Acked-by?
Hello Shuah,
friendly ping. Could you please respond with "Acked-by" if you don’t
mind me taking this patch via the s390 tree? Or let me know if you plan
to take it via your tree.
Thank you!
next prev parent reply other threads:[~2025-02-26 19:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 13:04 [PATCH v2] selftests/vDSO: fix GNU hash table entry size for s390x Thomas Weißschuh
2025-02-17 23:52 ` Vasily Gorbik
2025-02-26 19:37 ` Vasily Gorbik [this message]
2025-02-26 21:14 ` Shuah Khan
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=your-ad-here.call-01740598679-ext-1013@work.hours \
--to=gor@linux.ibm.com \
--cc=Jason@zx2c4.com \
--cc=hca@linux.ibm.com \
--cc=i@maskray.me \
--cc=jremus@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=thomas.weissschuh@linutronix.de \
--cc=xry111@xry111.site \
/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