From: Florian Fainelli <f.fainelli@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Doug Berger <opendmb@gmail.com>, Jason Baron <jbaron@akamai.com>,
David Rientjes <rientjes@google.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mm: include CMA pages in lowmem_reserve at boot
Date: Wed, 19 Aug 2020 10:30:25 -0700 [thread overview]
Message-ID: <50ad53dc-faf2-3014-bac3-be370b972f59@gmail.com> (raw)
In-Reply-To: <20200819102214.32238093b116ab6f1c5c7b73@linux-foundation.org>
On 8/19/20 10:22 AM, Andrew Morton wrote:
> On Wed, 19 Aug 2020 10:15:53 -0700 Florian Fainelli <f.fainelli@gmail.com> wrote:
>
>>>> In many cases the difference is not significant, but for example
>>>> an ARM platform with 1GB of memory and the following memory layout
>>>> [ 0.000000] cma: Reserved 256 MiB at 0x0000000030000000
>>>> [ 0.000000] Zone ranges:
>>>> [ 0.000000] DMA [mem 0x0000000000000000-0x000000002fffffff]
>>>> [ 0.000000] Normal empty
>>>> [ 0.000000] HighMem [mem 0x0000000030000000-0x000000003fffffff]
>>>>
>>>> would result in 0 lowmem_reserve for the DMA zone. This would allow
>>>> userspace to deplete the DMA zone easily.
>>>
>>> Sounds fairly serious for thos machines. Was a cc:stable considered?
>>
>> Since there is a Fixes: tag, it may have been assumed that the patch
>> would be picked up and as soon as it reaches Linus' tree it would be
>> picked up by the stable selection.
>
> It doesn't work that way - sometimes a fix isn't considered important
> enough to backport. It could just fix a typo in a comment!
Then can this be applied ASAP and back ported?
--
Florian
next prev parent reply other threads:[~2020-08-19 17:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 16:49 [PATCH v2] mm: include CMA pages in lowmem_reserve at boot Doug Berger
2020-08-19 3:18 ` Andrew Morton
2020-08-19 17:15 ` Florian Fainelli
2020-08-19 17:22 ` Andrew Morton
2020-08-19 17:30 ` Florian Fainelli [this message]
2020-08-19 17:40 ` Andrew Morton
2020-08-20 0:32 ` Doug Berger
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=50ad53dc-faf2-3014-bac3-be370b972f59@gmail.com \
--to=f.fainelli@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jbaron@akamai.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=opendmb@gmail.com \
--cc=rientjes@google.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).