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 v5 3/3] syscalls/modify_ldt01: Refactor into new API
Date: Mon, 31 Mar 2025 14:58:49 -0300 [thread overview]
Message-ID: <D8UNAKDAPZDW.I6DO8VJFXFVW@suse.com> (raw)
In-Reply-To: <D8UN8017EZT6.PVLFKG2ZOJT1@suse.com>
On Mon Mar 31, 2025 at 2:55 PM -03, Ricardo B. Marlière wrote:
> On Mon Mar 31, 2025 at 2:43 PM -03, rbm wrote:
(snip)
>> + * - Fails with EINVAL, when writing (func=1) to an invalid pointer
>> + * - Fails with EFAULT, when reading (func=0) from an invalid pointer
>> + * - Passes when reading (func=0) from a valid pointer
>
> Ah, I forgot to update the description...
>
/*\
* Verify that modify_ldt() calls:
*
* - Fails with EFAULT, when reading (func=0) from an invalid pointer
* - Passes when reading (func=0) from a valid pointer
* - Fails with EINVAL, when writing (func=1) to an invalid pointer
* - Fails with EINVAL, when writing (func=1) with an invalid bytecount value
* - Fails with EINVAL, when writing (func=1) an entry with invalid values
* - Fails with EINVAL, when writing (func=0x11) an entry with invalid values
*/
Thoughts?
- Ricardo.
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2025-03-31 17:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 17:43 [LTP] [PATCH v5 0/3] syscalls/modify_ldt: Refactor into new API Ricardo B. Marliere via ltp
2025-03-31 17:43 ` [LTP] [PATCH v5 1/3] syscalls/modify_ldt: Add lapi/ldt.h Ricardo B. Marliere via ltp
2025-04-01 8:48 ` Petr Vorel
2025-04-01 8:56 ` Andrea Cervesato via ltp
2025-04-01 10:21 ` Petr Vorel
2025-04-01 13:55 ` Ricardo B. Marli��re via ltp
2025-04-01 10:29 ` Petr Vorel
2025-04-01 10:45 ` Ricardo B. Marli��re via ltp
2025-03-31 17:43 ` [LTP] [PATCH v5 2/3] syscalls/modify_ldt02: Refactor into new API Ricardo B. Marliere via ltp
2025-03-31 17:43 ` [LTP] [PATCH v5 3/3] syscalls/modify_ldt01: " Ricardo B. Marliere via ltp
2025-03-31 17:55 ` Ricardo B. Marli��re via ltp
2025-03-31 17:58 ` Ricardo B. Marli��re via ltp [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=D8UNAKDAPZDW.I6DO8VJFXFVW@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 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.