From: Dan Carpenter <dan.carpenter@linaro.org>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: oe-kbuild@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>,
lkp@intel.com, oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
ying.huang@intel.com, Baolin Wang <baolin.wang@linux.alibaba.com>,
David Hildenbrand <david@redhat.com>,
John Hubbard <jhubbard@nvidia.com>, Mel Gorman <mgorman@suse.de>,
Ryan Roberts <ryan.roberts@arm.com>,
liushixin2@huawei.com
Subject: Re: [PATCH] mm: fix possible OOB in numa_rebuild_large_mapping()
Date: Wed, 12 Jun 2024 13:06:01 +0300 [thread overview]
Message-ID: <81da44d7-e07d-4757-9a67-87c35b62512c@moroto.mountain> (raw)
In-Reply-To: <c6df35cc-1331-4255-8ff5-898f6a911bec@huawei.com>
On Wed, Jun 12, 2024 at 10:50:02AM +0800, Kefeng Wang wrote:
> > b99a342d4f11a5 Huang Ying 2021-04-29 5364 out_map:
> > b99a342d4f11a5 Huang Ying 2021-04-29 5365 /*
> > b99a342d4f11a5 Huang Ying 2021-04-29 5366 * Make it present again, depending on how arch implements
> > b99a342d4f11a5 Huang Ying 2021-04-29 5367 * non-accessible ptes, some can allow access by kernel mode.
> > b99a342d4f11a5 Huang Ying 2021-04-29 5368 */
> > d2136d749d76af Baolin Wang 2024-03-29 5369 if (folio && folio_test_large(folio))
> >
> > Are folio_test_large() and folio_is_zone_device() mutually exclusive?
> > If so then this is a false positive. Just ignore the warning in that
> > case.
> >
>
> The folio in ZONE_DEVICE is not a large folio, so there is no issue for now,
> but will fix.
>
If it's not an issue, then don't feel obligated to do anything. These
are a one time email and then I treat it as addressed. These warnings
are intended to be useful, not a burden.
regards,
dan carpenter
next prev parent reply other threads:[~2024-06-12 10:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 10:32 Kefeng Wang
2024-06-07 10:37 ` David Hildenbrand
2024-06-12 2:41 ` Kefeng Wang
2024-06-09 16:03 ` Dan Carpenter
2024-06-09 20:53 ` Andrew Morton
2024-06-12 2:50 ` Kefeng Wang
2024-06-12 10:06 ` Dan Carpenter [this message]
2024-06-12 12:32 ` Kefeng Wang
2024-06-11 7:48 ` Baolin Wang
2024-06-11 10:34 ` David Hildenbrand
2024-06-11 12:32 ` David Hildenbrand
2024-06-12 1:16 ` Baolin Wang
2024-06-12 6:02 ` Kefeng Wang
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=81da44d7-e07d-4757-9a67-87c35b62512c@moroto.mountain \
--to=dan.carpenter@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=jhubbard@nvidia.com \
--cc=linux-mm@kvack.org \
--cc=liushixin2@huawei.com \
--cc=lkp@intel.com \
--cc=mgorman@suse.de \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=oe-kbuild@lists.linux.dev \
--cc=ryan.roberts@arm.com \
--cc=wangkefeng.wang@huawei.com \
--cc=ying.huang@intel.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