Re: [PATCH] mm/sparse: reset section's mem_map when fully deactivated

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Jan 16, 2020 at 11:18 AM Qian Cai <cai@xxxxxx> wrote:
>
>
>
> > On Jan 15, 2020, at 10:01 PM, Pingfan Liu <kernelfans@xxxxxxxxx> wrote:
> >
> > When fully deactivated, it is meaningless to keep the value of a section's
> > mem_map. And its mem_map will be reassigned during re-added.
> >
> > Beside this, it breaks the user space tool "makedumpfile", which makes
> > assumption that a hot-removed section having mem_map as NULL.
>
> Well, tools like makedumpfile and the crash utility always has to copy with

                            ^^^ cope ?
> low kernel implementation details changes like this. Why is it different this time?
Yeah, there are two direction. But as the first argument, it is
meaningless to keep the value.

Thanks,
Pingfan




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux