Linux Test Project
 help / color / mirror / Atom feed
From: "Ricardo B. Marlière via ltp" <ltp@lists.linux.it>
To: "Ricardo B. Marlière" <rbm@suse.com>,
	"Linux Test Project" <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v3] ldt.h: Add workaround for x86_64
Date: Tue, 20 May 2025 08:31:35 -0300	[thread overview]
Message-ID: <DA0YDBI0SQUN.2TLZFDRK8N1YD@suse.com> (raw)
In-Reply-To: <20250520-fixes-modify_ldt-v3-1-a78c79341d0c@suse.com>

On Tue May 20, 2025 at 8:29 AM -03, Ricardo B. Marlière wrote:
> From: Ricardo B. Marlière <rbm@suse.com>
>
> The commit be0aaca2f742 ("syscalls/modify_ldt: Add lapi/ldt.h") left behind
> an important factor of modify_ldt(): the kernel intentionally casts the
> return value to unsigned int. This was handled in
> testcases/cve/cve-2015-3290.c but was removed. Add it back to the relevant
> file.
>
> Reported-by: Martin Doucha <mdoucha@suse.cz>
> Reviewed-by: Martin Doucha <mdoucha@suse.cz>
> Signed-off-by: Ricardo B. Marlière <rbm@suse.com>
> ---
> Changes in v3:
> - EDITME: describe what is new in this series revision.
> - EDITME: use bulletpoints and terse descriptions.
> - Link to v2: https://lore.kernel.org/r/20250512-fixes-modify_ldt-v2-1-eaef5577e44e@suse.com

Changes in v3:
- Moved the `(rval == -1 && errno == EINVAL)` check into safe_modify_ldt.


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2025-05-20 11:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-20 11:29 [LTP] [PATCH v3] ldt.h: Add workaround for x86_64 Ricardo B. Marlière via ltp
2025-05-20 11:31 ` Ricardo B. Marlière via ltp [this message]
2025-05-20 11:34 ` Martin Doucha
2025-05-20 12:23   ` Andrea Cervesato via ltp
2025-05-20 14:17     ` Martin Doucha
2025-05-20 17:04       ` Andrea Cervesato via ltp
2025-05-20 17:29         ` Ricardo B. Marlière 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=DA0YDBI0SQUN.2TLZFDRK8N1YD@suse.com \
    --to=ltp@lists.linux.it \
    --cc=rbm@suse.com \
    /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