From: huangdengdui <huangdengdui@huawei.com>
To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>, <dev@dpdk.org>
Cc: <fengchengwen@huawei.com>, <lihuisong@huawei.com>,
<haijie1@huawei.com>, <liuyonglong@huawei.com>,
<roretzla@linux.microsoft.com>, <anatoly.burakov@intel.com>,
<stephen@networkplumber.org>, <mb@smartsharesystems.com>
Subject: Re: [PATCH] mem: fix infinite loop
Date: Thu, 3 Apr 2025 09:25:05 +0800 [thread overview]
Message-ID: <ec13baa6-ccbd-4e7d-897f-ae5cdc6834cd@huawei.com> (raw)
In-Reply-To: <a063308e-448d-4881-a661-17adb52888a4@gmail.com>
On 2025/4/3 5:16, Dmitry Kozlyuk wrote:
> On 02.04.2025 15:42, Dengdui Huang wrote:
>> When the process address space is insufficient,
>> mmap will fail, which will cause an infinite loop.
>> This pathc fix it.
>>
>> Fixes: c4b89ecb64ea ("eal: introduce memory management wrappers")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Dengdui Huang <huangdengdui@huawei.com>
>
> Acked-by: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
>
> Typo: "pathc fix" -> "patch fixes", or, better:
> "This patch stops attempting mmap if it fails and the requested size cannot be reduced."
>
> The bug is actually older, but it doesn't matter since both c4b89ecb64ea and b7cc54187ea4 belong to all LTS:
>
> Fixes: b7cc54187ea4 ("mem: move virtual area function in common directory")
>
It would be better to write the commit log like this, and I'll modify it in v2.
next prev parent reply other threads:[~2025-04-03 1:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 12:42 Dengdui Huang
2025-04-02 21:16 ` Dmitry Kozlyuk
2025-04-03 1:25 ` huangdengdui [this message]
2025-04-03 2:57 ` [PATCH v2] " Dengdui Huang
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=ec13baa6-ccbd-4e7d-897f-ae5cdc6834cd@huawei.com \
--to=huangdengdui@huawei.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=fengchengwen@huawei.com \
--cc=haijie1@huawei.com \
--cc=lihuisong@huawei.com \
--cc=liuyonglong@huawei.com \
--cc=mb@smartsharesystems.com \
--cc=roretzla@linux.microsoft.com \
--cc=stephen@networkplumber.org \
/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).