mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
	Christian Brauner <brauner@kernel.org>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Miaohe Lin <linmiaohe@huawei.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Tong Tiangen <tongtiangen@huawei.com>,
	Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH v2] mm: hwpoison: coredump: support recovery from dump_user_range()
Date: Tue, 18 Apr 2023 03:13:10 +0000	[thread overview]
Message-ID: <20230418031243.GA2845864@hori.linux.bs1.fc.nec.co.jp> (raw)
In-Reply-To: <20230417045323.11054-1-wangkefeng.wang@huawei.com>

On Mon, Apr 17, 2023 at 12:53:23PM +0800, Kefeng Wang wrote:
> The dump_user_range() is used to copy the user page to a coredump file,
> but if a hardware memory error occurred during copy, which called from
> __kernel_write_iter() in dump_user_range(), it crashes,
> 
>   CPU: 112 PID: 7014 Comm: mca-recover Not tainted 6.3.0-rc2 #425
>  
>   pc : __memcpy+0x110/0x260
>   lr : _copy_from_iter+0x3bc/0x4c8
>   ...
>   Call trace:
>    __memcpy+0x110/0x260
>    copy_page_from_iter+0xcc/0x130
>    pipe_write+0x164/0x6d8
>    __kernel_write_iter+0x9c/0x210
>    dump_user_range+0xc8/0x1d8
>    elf_core_dump+0x308/0x368
>    do_coredump+0x2e8/0xa40
>    get_signal+0x59c/0x788
>    do_signal+0x118/0x1f8
>    do_notify_resume+0xf0/0x280
>    el0_da+0x130/0x138
>    el0t_64_sync_handler+0x68/0xc0
>    el0t_64_sync+0x188/0x190
> 
> Generally, the '->write_iter' of file ops will use copy_page_from_iter()
> and copy_page_from_iter_atomic(), change memcpy() to copy_mc_to_kernel()
> in both of them to handle #MC during source read, which stop coredump
> processing and kill the task instead of kernel panic, but the source
> address may not always a user address, so introduce a new copy_mc flag in
> struct iov_iter{} to indicate that the iter could do a safe memory copy,
> also introduce the helpers to set/cleck the flag, for now, it's only
> used in coredump's dump_user_range(), but it could expand to any other
> scenarios to fix the similar issue.
> 
> Cc: Alexander Viro <viro@zeniv.linux.org.uk>
> Cc: Christian Brauner <brauner@kernel.org>
> Cc: Miaohe Lin <linmiaohe@huawei.com>
> Cc: Naoya Horiguchi <naoya.horiguchi@nec.com>
> Cc: Tong Tiangen <tongtiangen@huawei.com>
> Cc: Jens Axboe <axboe@kernel.dk>
> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
> ---
> v2:
> - move the helper functions under pre-existing CONFIG_ARCH_HAS_COPY_MC
> - reposition the copy_mc in struct iov_iter for easy merge, suggested
>   by Andrew Morton
> - drop unnecessary clear flag helper
> - fix checkpatch warning
>  fs/coredump.c       |  1 +
>  include/linux/uio.h | 16 ++++++++++++++++
>  lib/iov_iter.c      | 17 +++++++++++++++--
>  3 files changed, 32 insertions(+), 2 deletions(-)
> 
...
> @@ -371,6 +372,14 @@ size_t _copy_mc_to_iter(const void *addr, size_t bytes, struct iov_iter *i)
>  EXPORT_SYMBOL_GPL(_copy_mc_to_iter);
>  #endif /* CONFIG_ARCH_HAS_COPY_MC */
>  
> +static void *memcpy_from_iter(struct iov_iter *i, void *to, const void *from,
> +				 size_t size)
> +{
> +	if (iov_iter_is_copy_mc(i))
> +		return (void *)copy_mc_to_kernel(to, from, size);

Is it helpful to call memory_failure_queue() if copy_mc_to_kernel() fails
due to a memory error?

Thanks,
Naoya Horiguchi

> +	return memcpy(to, from, size);
> +}
> +
>  size_t _copy_from_iter(void *addr, size_t bytes, struct iov_iter *i)
>  {
>  	if (WARN_ON_ONCE(!i->data_source))

  reply	other threads:[~2023-04-18  3:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-17  4:53 Kefeng Wang
2023-04-18  3:13 ` HORIGUCHI NAOYA(堀口 直也) [this message]
2023-04-18  9:45   ` Kefeng Wang
2023-04-19  7:25     ` HORIGUCHI NAOYA(堀口 直也)
2023-04-19 12:03       ` Kefeng Wang
2023-04-20  2:03         ` Jane Chu
2023-04-20  2:59           ` Kefeng Wang
2023-04-20 15:05             ` Kefeng Wang
2023-04-21  3:13               ` HORIGUCHI NAOYA(堀口 直也)
2023-04-21  5:43                 ` Kefeng Wang
2023-04-24  6:44                   ` HORIGUCHI NAOYA(堀口 直也)
2023-04-24 16:17                     ` Luck, Tony
2023-04-25  1:47                       ` Kefeng Wang
2023-04-25 17:16                         ` Luck, Tony
2023-04-26  1:23                           ` Kefeng Wang
2023-04-26 15:45                             ` Luck, Tony
2023-04-27  1:06                               ` Kefeng Wang
2023-04-27  2:31                                 ` HORIGUCHI NAOYA(堀口 直也)
2023-04-27 16:45                                   ` Luck, Tony
2023-04-28  8:59                                     ` Kefeng Wang
2023-04-28  8:56                                   ` 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=20230418031243.GA2845864@hori.linux.bs1.fc.nec.co.jp \
    --to=naoya.horiguchi@nec.com \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=brauner@kernel.org \
    --cc=linmiaohe@huawei.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=tongtiangen@huawei.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=wangkefeng.wang@huawei.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

all inboxes | Powered by JetHome®