Re: [PATCH 0/3] kexec/memory_hotplug: Prevent removal and accidental use

2020-04-22 Thread James Morse
Hi Eric, On 22/04/2020 14:04, Eric W. Biederman wrote: > James Morse writes: >> On 15/04/2020 21:29, Eric W. Biederman wrote: >>> James Morse writes: arm64 recently queued support for memory hotremove, which led to some new corner cases for kexec. If the kexec segments are

Re: [PATCH 0/3] kexec/memory_hotplug: Prevent removal and accidental use

2020-04-22 Thread Eric W. Biederman
James Morse writes: > Hi Eric, > > On 15/04/2020 21:29, Eric W. Biederman wrote: >> James Morse writes: >> >>> Hello! >>> >>> arm64 recently queued support for memory hotremove, which led to some >>> new corner cases for kexec. >>> >>> If the kexec segments are loaded for a removable region,

Re: [PATCH 0/3] kexec/memory_hotplug: Prevent removal and accidental use

2020-04-22 Thread James Morse
Hi Eric, On 15/04/2020 21:29, Eric W. Biederman wrote: > James Morse writes: > >> Hello! >> >> arm64 recently queued support for memory hotremove, which led to some >> new corner cases for kexec. >> >> If the kexec segments are loaded for a removable region, that region may >> be removed before

Re: [PATCH 0/3] kexec/memory_hotplug: Prevent removal and accidental use

2020-04-15 Thread Eric W. Biederman
James Morse writes: > Hello! > > arm64 recently queued support for memory hotremove, which led to some > new corner cases for kexec. > > If the kexec segments are loaded for a removable region, that region may > be removed before kexec actually occurs. This causes the first kernel to > lockup

Re: [PATCH 0/3] kexec/memory_hotplug: Prevent removal and accidental use

2020-04-14 Thread James Morse
Hi Dave, On 31/03/2020 04:46, Dave Young wrote: > I agreed that file load is still not widely used, but in the long run > we should not maintain both of them all the future time. Especially > when some kernel-userspace interfaces need to be introduced, file load > will have the natural

Re: [PATCH 0/3] kexec/memory_hotplug: Prevent removal and accidental use

2020-03-30 Thread Dave Young
Hi James, On 03/30/20 at 06:17pm, James Morse wrote: > Hi Baoquan, > > On 3/30/20 2:55 PM, Baoquan He wrote: > > On 03/26/20 at 06:07pm, James Morse wrote: > >> arm64 recently queued support for memory hotremove, which led to some > >> new corner cases for kexec. > >> > >> If the kexec segments

Re: [PATCH 0/3] kexec/memory_hotplug: Prevent removal and accidental use

2020-03-30 Thread Dave Young
Hi James, On 03/26/20 at 06:07pm, James Morse wrote: > Hello! > > arm64 recently queued support for memory hotremove, which led to some > new corner cases for kexec. > > If the kexec segments are loaded for a removable region, that region may > be removed before kexec actually occurs. This

Re: [PATCH 0/3] kexec/memory_hotplug: Prevent removal and accidental use

2020-03-30 Thread James Morse
Hi Baoquan, On 3/30/20 2:55 PM, Baoquan He wrote: > On 03/26/20 at 06:07pm, James Morse wrote: >> arm64 recently queued support for memory hotremove, which led to some >> new corner cases for kexec. >> >> If the kexec segments are loaded for a removable region, that region may >> be removed

Re: [PATCH 0/3] kexec/memory_hotplug: Prevent removal and accidental use

2020-03-30 Thread Baoquan He
Hi James, On 03/26/20 at 06:07pm, James Morse wrote: > Hello! > > arm64 recently queued support for memory hotremove, which led to some > new corner cases for kexec. > > If the kexec segments are loaded for a removable region, that region may > be removed before kexec actually occurs. This

Re: [PATCH 0/3] kexec/memory_hotplug: Prevent removal and accidental use

2020-03-30 Thread David Hildenbrand
On 27.03.20 16:42, James Morse wrote: > Hi David, > > On 3/27/20 9:27 AM, David Hildenbrand wrote: >> On 26.03.20 19:07, James Morse wrote: >>> arm64 recently queued support for memory hotremove, which led to some >>> new corner cases for kexec. >>> >>> If the kexec segments are loaded for a

Re: [PATCH 0/3] kexec/memory_hotplug: Prevent removal and accidental use

2020-03-27 Thread James Morse
Hi David, On 3/27/20 9:27 AM, David Hildenbrand wrote: > On 26.03.20 19:07, James Morse wrote: >> arm64 recently queued support for memory hotremove, which led to some >> new corner cases for kexec. >> >> If the kexec segments are loaded for a removable region, that region may >> be removed

Re: [PATCH 0/3] kexec/memory_hotplug: Prevent removal and accidental use

2020-03-27 Thread James Morse
Hi Baoquan, On 3/27/20 2:11 AM, Baoquan He wrote: > On 03/26/20 at 06:07pm, James Morse wrote: >> arm64 recently queued support for memory hotremove, which led to some >> new corner cases for kexec. >> >> If the kexec segments are loaded for a removable region, that region may >> be removed

Re: [PATCH 0/3] kexec/memory_hotplug: Prevent removal and accidental use

2020-03-27 Thread David Hildenbrand
On 26.03.20 19:07, James Morse wrote: > Hello! > > arm64 recently queued support for memory hotremove, which led to some > new corner cases for kexec. > > If the kexec segments are loaded for a removable region, that region may > be removed before kexec actually occurs. This causes the first

Re: [PATCH 0/3] kexec/memory_hotplug: Prevent removal and accidental use

2020-03-26 Thread Baoquan He
On 03/26/20 at 06:07pm, James Morse wrote: > Hello! > > arm64 recently queued support for memory hotremove, which led to some > new corner cases for kexec. > > If the kexec segments are loaded for a removable region, that region may > be removed before kexec actually occurs. This causes the

[PATCH 0/3] kexec/memory_hotplug: Prevent removal and accidental use

2020-03-26 Thread James Morse
Hello! arm64 recently queued support for memory hotremove, which led to some new corner cases for kexec. If the kexec segments are loaded for a removable region, that region may be removed before kexec actually occurs. This causes the first kernel to lockup when applying the relocations. (I've