From: Petr Vorel <pvorel@suse.cz>
To: Wei Gao <wegao@suse.com>,
ltp@lists.linux.it, Andrea Cervesato <andrea.cervesato@suse.com>
Subject: Re: [LTP] [PATCH v2] mseal02: Handle multiple errnos for 32-bit compat mode
Date: Fri, 20 Mar 2026 18:27:18 +0100 [thread overview]
Message-ID: <20260320172718.GA163304@pevik> (raw)
In-Reply-To: <20260320150945.GA160532@pevik>
Hi Wei, all,
> Hi all,
> > In 32-bit compat mode, the overflow_size (calculated using a 32-bit ULONG_MAX)
> > does not cause a 64-bit integer wrap-around when added to the start address.
> > Consequently, the kernel see valid range that points to unmapped space, returning
> > ENOMEM instead of the expected EINVAL.
> Also LGTM.
> Reviewed-by: Petr Vorel <pvorel@suse.cz>
> + if (tst_is_compat_mode())
> + tcases[2].exp_err = ENOMEM;
I was about to merge, but thinking about it twice, it'd make sense instead
hardcoding index 2 (we talked about it in the past, that hardcoding indexes can
cause problems the future) to add attribute .check_kver, similar way Jan Polensky
did in dcf0c145d9 ("setxattr02: Adapt test for kernel 7.1.0+ socket xattr support").
Could you please modify it in v3?
Kind regards,
Petr
[1] https://github.com/linux-test-project/ltp/commit/dcf0c145d90531b919e633bb3f481f59a867aa06
> Kind regards,
> Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-03-20 17:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 0:28 [LTP] [PATCH v1] mseal02: Handle multiple errnos for 32-bit compat mode Wei Gao via ltp
2026-02-18 13:34 ` Andrea Cervesato via ltp
2026-02-19 11:37 ` Cyril Hrubis
2026-02-26 2:25 ` [LTP] [PATCH v2] " Wei Gao via ltp
2026-03-20 14:35 ` Andrea Cervesato via ltp
2026-03-20 15:09 ` Petr Vorel
2026-03-20 17:27 ` Petr Vorel [this message]
2026-03-23 6:08 ` [LTP] [PATCH v3] " Wei Gao via ltp
2026-03-23 13:14 ` Cyril Hrubis
2026-03-26 10:07 ` Andrea Cervesato via ltp
2026-03-26 10:08 ` Andrea Cervesato via ltp
2026-03-26 10:43 ` Petr Vorel
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=20260320172718.GA163304@pevik \
--to=pvorel@suse.cz \
--cc=andrea.cervesato@suse.com \
--cc=ltp@lists.linux.it \
--cc=wegao@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.