From: Cyril Hrubis <chrubis@suse.cz>
To: Tarun Sahu <tsahu@linux.ibm.com>
Cc: sbhat@linux.ibm.com, aneesh.kumar@linux.ibm.com,
geetika@linux.ibm.com, vaibhav@linux.ibm.com,
rpalethorpe@suse.com, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v6 2/4] Hugetlb: Migrating libhugetlbfs brk_near_huge
Date: Thu, 3 Nov 2022 11:01:51 +0100 [thread overview]
Message-ID: <Y2ORjzDvZppk8PTl@rei> (raw)
In-Reply-To: <20221103054317.499221-3-tsahu@linux.ibm.com>
Hi!
> +/*\
> + *
> + * [Description]
> + *
> + * brk near hugepage:
^
and this bit is still here
If you have asciidoc installed you can run make in the top level LTP
directory which will generate docparse/metadata.html where you can check
how the documentation is rendered.
> + * Certain kernels have a bug where brk() does not perform the same
> + * checks that a MAP_FIXED mmap() will, allowing brk() to create a
> + * normal page VMA in a hugepage only address region. This can lead
> + * to oopses or other badness.
> + */
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-11-03 10:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 5:43 [LTP] [PATCH v6 0/4] Hugetlb:Migrating the libhugetlbfs tests Tarun Sahu
2022-11-03 5:43 ` [LTP] [PATCH v6 1/4] Hugetlb: Add new tst_test options for hugeltb test support Tarun Sahu
2022-11-03 6:08 ` Li Wang
2022-11-03 9:31 ` Tarun Sahu
2022-11-03 9:55 ` Li Wang
2022-11-03 9:45 ` Cyril Hrubis
2022-11-03 5:43 ` [LTP] [PATCH v6 2/4] Hugetlb: Migrating libhugetlbfs brk_near_huge Tarun Sahu
2022-11-03 9:55 ` Cyril Hrubis
2022-11-03 10:01 ` Cyril Hrubis [this message]
2022-11-03 5:43 ` [LTP] [PATCH v6 3/4] Hugetlb: Migrating libhugetlbfs chunk-overcommit Tarun Sahu
2022-11-03 5:43 ` [LTP] [PATCH v6 4/4] Hugetlb: Migrating libhugetlbfs corrupt-by-cow-opt Tarun Sahu
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=Y2ORjzDvZppk8PTl@rei \
--to=chrubis@suse.cz \
--cc=aneesh.kumar@linux.ibm.com \
--cc=geetika@linux.ibm.com \
--cc=ltp@lists.linux.it \
--cc=rpalethorpe@suse.com \
--cc=sbhat@linux.ibm.com \
--cc=tsahu@linux.ibm.com \
--cc=vaibhav@linux.ibm.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