Messages in this thread | | | Date | Thu, 12 Oct 2023 16:57:08 +0200 | From | Borislav Petkov <> | Subject | Re: [PATCH RESEND v2] x86/mce: Set PG_hwpoison page flag to avoid the capture kernel panic |
| |
On Wed, Oct 11, 2023 at 11:00:57AM +0800, Zhiquan Li wrote: > Aha, this is the neat thing about the patch. The main task of kdump > kernel is providing a "window" - /proc/vmcore, for the dump program to > access old memory. A dump program running in userspace determines the > "policy". Which pages need to be dumped is determined by the > configuration of dump program, it reads out the pages that the > sustaining engineer is interested in and excludes the rest. The de > facto dump program (makedumpfile) already supports to identify those > poisoned pages and exclude them a decade ago:
Yes, put that in your commit message.
> When we were developing the patch internally, Tony contributed a lot of > precious ideas and guidance, not only the code change he mentioned in > commit message. > > The previous V2 sent by Tony missed the merge window of v6.5, so I > re-based it onto the latest v6.6 rc, re-validated and re-send the patch. > And I will follow up the feedback from community.
Then you should ask Tony whether he wants Co-developed-by:. See
Documentation/process/submitting-patches.rst
for detail.
There it is also explained what an SOB chain is and how it should look like.
Thx.
-- Regards/Gruss, Boris.
https://people.kernel.org/tglx/notes-about-netiquette
| |