From: Shuah Khan <skhan@linuxfoundation.org>
To: Raghavendra Rao Ananta <rananta@google.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
linux-kselftest@vger.kernel.org, stable@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] selftests/rseq: Fix rseq for cases without glibc support
Date: Mon, 13 Jan 2025 16:06:39 -0700 [thread overview]
Message-ID: <15339541-8912-4a1f-b5ca-26dd825dfb88@linuxfoundation.org> (raw)
In-Reply-To: <20241210224435.15206-1-rananta@google.com>
On 12/10/24 15:44, Raghavendra Rao Ananta wrote:
> Currently the rseq constructor, rseq_init(), assumes that glibc always
> has the support for rseq symbols (__rseq_size for instance). However,
> glibc supports rseq from version 2.35 onwards. As a result, for the
> systems that run glibc less than 2.35, the global rseq_size remains
> initialized to -1U. When a thread then tries to register for rseq,
> get_rseq_min_alloc_size() would end up returning -1U, which is
> incorrect. Hence, initialize rseq_size for the cases where glibc doesn't
> have the support for rseq symbols.
>
> Cc: stable@vger.kernel.org
> Fixes: 73a4f5a704a2 ("selftests/rseq: Fix mm_cid test failure")
> Signed-off-by: Raghavendra Rao Ananta <rananta@google.com>
> ---
Applied to linux_kselftest next for Linux 6.14-rc1 after fixing the
commit if for Fixes tag
thanks,
-- Shuah
next prev parent reply other threads:[~2025-01-13 23:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 22:44 [PATCH] selftests/rseq: Fix rseq for cases without glibc support Raghavendra Rao Ananta
2025-01-13 23:06 ` Shuah Khan [this message]
2025-01-14 14:07 ` Mathieu Desnoyers
2025-01-14 14:27 ` Mathieu Desnoyers
2025-01-14 16:12 ` 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=15339541-8912-4a1f-b5ca-26dd825dfb88@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rananta@google.com \
--cc=stable@vger.kernel.org \
/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