From: Andrew Morton <akpm@linux-foundation.org>
To: Patrick Wang <patrick.wang.shcn@gmail.com>
Cc: catalin.marinas@arm.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: kmemleak: take a full lowmem check in kmemleak_*_phys()
Date: Wed, 13 Apr 2022 12:28:26 -0700 [thread overview]
Message-ID: <20220413122826.792a859d90b6c2822b1c796a@linux-foundation.org> (raw)
In-Reply-To: <20220413122925.33856-1-patrick.wang.shcn@gmail.com>
On Wed, 13 Apr 2022 20:29:25 +0800 Patrick Wang <patrick.wang.shcn@gmail.com> wrote:
> The kmemleak_*_phys() apis do not check the address for lowmem's min
> boundary, while the caller may pass an address below lowmem, which
> will trigger an oops:
Do you believe this fix should be backported into -stable kernels?
next prev parent reply other threads:[~2022-04-13 19:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 12:29 Patrick Wang
2022-04-13 19:28 ` Andrew Morton [this message]
2022-04-14 2:40 ` patrick wang
2022-04-14 17:26 ` Catalin Marinas
2022-05-27 4:00 ` Yee Lee
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=20220413122826.792a859d90b6c2822b1c796a@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=patrick.wang.shcn@gmail.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