From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v6] Refactor fork14 using new LTP API
Date: Wed, 15 May 2024 15:17:19 +0200 [thread overview]
Message-ID: <20240515131719.GB220651@pevik> (raw)
In-Reply-To: <20240503081647.18253-1-andrea.cervesato@suse.de>
Hi Andrea,
...
> +/*\
> + * [Description]
> *
> * This test is a reporducer for this patch:
s/reporducer/reproducer/
> + * https://lore.kernel.org/lkml/1335289853-2923-1-git-send-email-siddhesh.poyarekar@gmail.com/
> * Since vma length in dup_mmap is calculated and stored in a unsigned
> * int, it will overflow when length of mmaped memory > 16 TB. When
> + * overflow occurs, fork will incorrectly succeed. The patch above fixed it.
> + */
nit: this has been merged to mainline long time ago (kernel 3.5). I'll change before merge to:
/*\
* [Description]
*
* This test is a reproducer for kernel 3.5:
* 7edc8b0ac16c ("mm/fork: fix overflow in vma length when copying mmap on clone")
*
* Since VMA length in dup_mmap() is calculated and stored in a unsigned
* int, it will overflow when length of mmaped memory > 16 TB. When
* overflow occurs, fork will incorrectly succeed. The patch above fixed it.
*/
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2024-05-15 13:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 8:16 [LTP] [PATCH v6] Refactor fork14 using new LTP API Andrea Cervesato
2024-05-03 12:49 ` Martin Doucha
2024-05-06 20:26 ` Petr Vorel
2024-05-07 7:24 ` Andrea Cervesato via ltp
2024-05-15 14:22 ` Petr Vorel
2024-05-15 14:25 ` Cyril Hrubis
2024-05-15 23:10 ` Petr Vorel
2024-05-15 14:25 ` Andrea Cervesato via ltp
2024-05-15 13:17 ` Petr Vorel [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=20240515131719.GB220651@pevik \
--to=pvorel@suse.cz \
--cc=andrea.cervesato@suse.de \
--cc=ltp@lists.linux.it \
/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).