From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: "HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>
Cc: "Luck, Tony" <tony.luck@intel.com>,
"chu, jane" <jane.chu@oracle.com>,
Thomas Gleixner <tglx@linutronix.de>,
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: Fri, 28 Apr 2023 16:56:49 +0800 [thread overview]
Message-ID: <c7eb49e4-2382-00d4-01e5-aac114ad9931@huawei.com> (raw)
In-Reply-To: <20230427023045.GA3499768@hori.linux.bs1.fc.nec.co.jp>
On 2023/4/27 10:31, HORIGUCHI NAOYA(堀口 直也) wrote:
> On Thu, Apr 27, 2023 at 09:06:46AM +0800, Kefeng Wang wrote:
>>
>>
...
>> For coredump，the task work will be called too, see following code,
>>
>> get_signal
>> sig_kernel_coredump
>> elf_core_dump
>> dump_user_range
>> _copy_from_iter // with MC-safe copy, return without panic
>> do_group_exit(ksig->info.si_signo);
>> do_exit
>> exit_task_work
>> task_work_run
>> kill_me_never
>> memory_failure
>>
>> I also add debug print to check the memory_failure() processing after
>> add MCE_IN_KERNEL_COPYIN to MCE_SAFE exception type, also tested CoW of
>> normal page and huge page, it works too.
>
> Sounds nice to me.
> Maybe this information is worth documenting in the patch description.
>
Sure, will make a formal patch and send out, thanks.
> Thanks,
> Naoya Horiguchi
prev parent reply other threads:[~2023-04-28 8:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 4:53 Kefeng Wang
[not found] ` <20230418031243.GA2845864@hori.linux.bs1.fc.nec.co.jp>
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 [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=c7eb49e4-2382-00d4-01e5-aac114ad9931@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=jane.chu@oracle.com \
--cc=linmiaohe@huawei.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=naoya.horiguchi@nec.com \
--cc=tglx@linutronix.de \
--cc=tongtiangen@huawei.com \
--cc=tony.luck@intel.com \
--cc=viro@zeniv.linux.org.uk \
/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