From: "H.J. Lu" <hjl.tools@gmail.com>
To: "Willgerodt, Felix" <felix.willgerodt@intel.com>
Cc: GDB <gdb-patches@sourceware.org>, John Baldwin <jhb@freebsd.org>
Subject: Re: [PATCH] gdbserver: Clear X86_XSTATE_MPX bits in xcr0 on x32
Date: Wed, 20 Mar 2024 03:48:13 -0700 [thread overview]
Message-ID: <CAMe9rOpxVQji7y=XP-kEh6_1AzK0rF=AbUNcx4yTkgjwcVzZBA@mail.gmail.com> (raw)
In-Reply-To: <MN2PR11MB456679AF9189CCFA765DABEA8E332@MN2PR11MB4566.namprd11.prod.outlook.com>
On Wed, Mar 20, 2024 at 1:40 AM Willgerodt, Felix
<felix.willgerodt@intel.com> wrote:
>
> > -----Original Message-----
> > From: H.J. Lu <hjl.tools@gmail.com>
> > Sent: Dienstag, 19. März 2024 19:36
> > To: GDB <gdb-patches@sourceware.org>; John Baldwin <jhb@freebsd.org>;
> > Willgerodt, Felix <felix.willgerodt@intel.com>
> > Subject: [PATCH] gdbserver: Clear X86_XSTATE_MPX bits in xcr0 on x32
> >
> > Since MPX isn't available for x32, we should clear X86_XSTATE_MPX bits
> > on x32.
> >
> > PR server/31511
> > * linux-x86-low.cc (x86_linux_read_description): Clear
> > X86_XSTATE_MPX bits in xcr0 on x32.
> > ---
> > gdbserver/linux-x86-low.cc | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/gdbserver/linux-x86-low.cc b/gdbserver/linux-x86-low.cc
> > index 3af0a009052..28b5d523b8e 100644
> > --- a/gdbserver/linux-x86-low.cc
> > +++ b/gdbserver/linux-x86-low.cc
> > @@ -938,6 +938,10 @@ x86_linux_read_description (void)
> > xcr0 = xstateregs[(I386_LINUX_XSAVE_XCR0_OFFSET
> > / sizeof (uint64_t))];
> >
> > + /* No MPX on x32. */
> > + if (!is_elf64)
> > + xcr0 &= ~X86_XSTATE_MPX;
> > +
>
> Doesn't that also disable it for 32-bit?
Fixed in the v2 patch with
+ /* No MPX on x32. */
+ if (machine == EM_X86_64 && !is_elf64)
+ xcr0 &= ~X86_XSTATE_MPX;
+
> x86_target::low_siginfo_fixup() uses this to check x32:
>
> /* No fixup for native x32 GDB. */
> else if (!is_elf64 && sizeof (void *) == 8)
>
>
Thanks.
--
H.J.
prev parent reply other threads:[~2024-03-20 10:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240319152558.45742-1-hjl.tools@gmail.com>
2024-03-19 18:36 ` H.J. Lu
2024-03-20 8:40 ` Willgerodt, Felix
2024-03-20 10:48 ` H.J. Lu [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='CAMe9rOpxVQji7y=XP-kEh6_1AzK0rF=AbUNcx4yTkgjwcVzZBA@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=felix.willgerodt@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=jhb@freebsd.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).