[PATCH v2 0/2] Allow to kexec with initramfs larger than 2G

Currently, the largest initramfs that is supported by kexec_file_load() syscall is 2G. This is because kernel_read_file() returns int, and is limited to INT_MAX or 2G. On the other hand, there are kexec based boot loaders (i.e. u-root), that may need to boot netboot images that might be larger

[PATCH v2 1/2] fs/kernel_read_file: Allow to read files up-to ssize_t

Currently, the maximum file size that is supported is 2G. This may be too small in some cases. For example, kexec_file_load() system call loads initramfs. In some netboot cases initramfs can be rather large. Allow to use up-to ssize_t bytes. The callers still can limit the maximum file size via

[PATCH v2 2/2] kexec_file: Increase maximum file size to 4G

In some case initrd can be large. For example, it could be a netboot image loaded by u-root, that is kexec'ing into it. The maximum size of initrd is arbitrary set to 2G. Also, the limit is not very obvious because it is hidden behind a generic INT_MAX macro. Theoretically, we could make it

Re: [PATCH] kexec_file: Increase maximum file size to 4G

On Thu, May 26, 2022 at 4:45 PM Pasha Tatashin wrote: > > On Thu, May 26, 2022 at 4:38 PM Pasha Tatashin > wrote: > > > > In some case initrd can be large. For example, it could be a netboot > > image loaded by u-root, that is kexec'ing into it. > > > > The maximum size of initrd is arbitrary

Re: [PATCH] kexec_file: Increase maximum file size to 4G

On Thu, May 26, 2022 at 4:38 PM Pasha Tatashin wrote: > > In some case initrd can be large. For example, it could be a netboot > image loaded by u-root, that is kexec'ing into it. > > The maximum size of initrd is arbitrary set to 2G. Also, the limit is > not very obvious because it is hidden

[PATCH] kexec_file: Increase maximum file size to 4G

In some case initrd can be large. For example, it could be a netboot image loaded by u-root, that is kexec'ing into it. The maximum size of initrd is arbitrary set to 2G. Also, the limit is not very obvious because it is hidden behind a generic INT_MAX macro. Theoretically, we could make it

Inquiry

Good day, We are interested in doing business with your company and we hope to establish a lasting business relationship. Kindly provide your updated catalogue for our reference and to enable us to prepare our official order. I look forward to your reply. Regards, Saumen Taraphdar Purchase

Re: [PATCH v8 0/7] crash: Kernel handling of CPU and memory hot un/plug

Hello Eric, On 26/05/22 18:46, Eric DeVolder wrote: On 5/25/22 10:13, Sourabh Jain wrote: Hello Eric, On 06/05/22 00:15, Eric DeVolder wrote: When the kdump service is loaded, if a CPU or memory is hot un/plugged, the crash elfcorehdr (for x86), which describes the CPUs and memory in the

Re: [PATCH v8 0/7] crash: Kernel handling of CPU and memory hot un/plug

On 5/26/22 08:39, Sourabh Jain wrote: Hello Eric, On 26/05/22 18:46, Eric DeVolder wrote: On 5/25/22 10:13, Sourabh Jain wrote: Hello Eric, On 06/05/22 00:15, Eric DeVolder wrote: When the kdump service is loaded, if a CPU or memory is hot un/plugged, the crash elfcorehdr (for x86),

Re: [PATCH v8 0/7] crash: Kernel handling of CPU and memory hot un/plug

On 5/25/22 10:13, Sourabh Jain wrote: Hello Eric, On 06/05/22 00:15, Eric DeVolder wrote: When the kdump service is loaded, if a CPU or memory is hot un/plugged, the crash elfcorehdr (for x86), which describes the CPUs and memory in the system, must also be updated, else the resulting vmcore

Re: [PATCH] kexec_file: Drop weak attribute from arch_kexec_apply_relocations[_add]

Andrew Morton wrote: On Fri, 20 May 2022 14:25:05 -0500 "Eric W. Biederman" wrote: > I am not strongly against taking off __weak, just wondering if there's > chance to fix it in recordmcount, and the cost comparing with kernel fix; > except of this issue, any other weakness of __weak.