From: wang lian <lianux.mm@gmail.com>
To: ziy@nvidia.com
Cc: Liam.Howlett@oracle.com, akpm@linux-foundation.org,
brauner@kernel.org, broonie@kernel.org, david@redhat.com,
gkwang@linx-info.com, jannh@google.com, lianux.mm@gmail.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-mm@kvack.org, lorenzo.stoakes@oracle.com,
p1ucky0923@gmail.com, ryncsn@gmail.com, shuah@kernel.org,
sj@kernel.org, vbabka@suse.cz, zijing.zhang@proton.me
Subject: Re: [PATCH v6] selftests/mm: add process_madvise() tests
Date: Wed, 23 Jul 2025 19:30:44 +0800 [thread overview]
Message-ID: <20250723113044.40876-1-lianux.mm@gmail.com> (raw)
In-Reply-To: <1C468AC6-C55B-41A3-9335-65B03EF65B83@nvidia.com>
> Here an invalid address range is provided, since pid is checked before
> address ranges are checked.
> BTW, the size of iovec array cannot be bigger than IOV_MAX. It might be
> worth testing as well, if you want to.
> With default_huge_page_size() -> read_pmd_pagesize() fix, feel free to
> add:
> Reviewed-by: Zi Yan <ziy@nvidia.com>
> Tested-by: Zi Yan <ziy@nvidia.com>
> I am able to compile and run the test on arm64. Thanks.
> Best Regards,
> Yan, Zi
Hi Zi,
Thanks a lot for your review and the valuable feedback! The issues you've pointed out are very helpful.
Regarding the logic where the PID is checked before the address ranges,
that was an oversight on my part and I will fix it.
I'll also add the test case for the iovec array size against IOV_MAX as you suggested.
And thank you for adding your Reviewed-by and Tested-by tags when i fix this.
I plan to collect all the review comments, revise the patches, and send out a new version
with your tags included in the next 2-3 days.
Thanks again!
Best Regards,
Wang Lian
prev parent reply other threads:[~2025-07-23 11:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 11:46 [PATCH v6] selftests/mm: add process_madvise() tests wang lian
2025-07-23 0:30 ` Zi Yan
2025-07-23 11:05 ` wang lian
2025-07-23 11:30 ` wang lian [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=20250723113044.40876-1-lianux.mm@gmail.com \
--to=lianux.mm@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=broonie@kernel.org \
--cc=david@redhat.com \
--cc=gkwang@linx-info.com \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=p1ucky0923@gmail.com \
--cc=ryncsn@gmail.com \
--cc=shuah@kernel.org \
--cc=sj@kernel.org \
--cc=vbabka@suse.cz \
--cc=zijing.zhang@proton.me \
--cc=ziy@nvidia.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;
as well as URLs for NNTP newsgroup(s).