public inbox for linux-mm@kvack.org
 help / color / mirror / Atom feed
From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Jane Chu <jane.chu@oracle.com>, <pmladek@suse.com>,
	<rostedt@goodmis.org>, <senozhatsky@chromium.org>,
	<andriy.shevchenko@linux.intel.com>, <linux@rasmusvillemoes.dk>,
	<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>
Cc: <konrad.wilk@oracle.com>, <haakon.bugge@oracle.com>,
	<john.haxby@oracle.com>
Subject: Re: [PATCH v3 0/1] vsprintf: check non-canonical pointer by kern_addr_valid()
Date: Thu, 20 Oct 2022 21:12:57 +0800	[thread overview]
Message-ID: <dadd98ef-c2d8-fe9b-5aca-00c31d7a65c7@huawei.com> (raw)
In-Reply-To: <20221019193431.2923462-1-jane.chu@oracle.com>


On 2022/10/20 3:34, Jane Chu wrote:
> Changes since v2 [1]:
>   - revised commit comment for clarification;
>   - cc linux-mm for expert's review on the kern_addr_valid() usage as suggested by Petr;

but this won't fix issue on archs which don't have correct 
kern_addr_valid(), right?

could we call copy_from_kernel_nofault() when it could works well, and 
skip it on early boot?

other options, call some functions in include/asm-generic/sections.h  or 
include/linux/kallsyms.h?


>   - cc Kefeng Wang in light of his recent patch [2]
>
> [1]: https://lore.kernel.org/lkml/288a7aba-c647-b51f-bdb3-99a62449dbb3@oracle.com/T/
> [2]: https://lore.kernel.org/lkml/20221018074014.185687-1-wangkefeng.wang@huawei.com/
>
> Jane Chu (1):
>    vsprintf: protect kernel from panic due to non-canonical pointer
>      dereference
>
>   lib/vsprintf.c | 3 +++
>   1 file changed, 3 insertions(+)
>


      parent reply	other threads:[~2022-10-20 13:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19 19:34 [PATCH v3 0/1] vsprintf: check non-canonical pointer by kern_addr_valid() Jane Chu
2022-10-19 19:34 ` [PATCH v3 1/1] vsprintf: protect kernel from panic due to non-canonical pointer dereference Jane Chu
2022-10-20 11:41   ` kernel test robot
2022-10-20 13:12 ` Kefeng Wang [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=dadd98ef-c2d8-fe9b-5aca-00c31d7a65c7@huawei.com \
    --to=wangkefeng.wang@huawei.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=haakon.bugge@oracle.com \
    --cc=jane.chu@oracle.com \
    --cc=john.haxby@oracle.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.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