* Kees Cook wrote:
> > So can we rename it to something more expressive, such as kernel_total_size
> > or
> > so?
>
> You got it. Thanks again for digging through all this!
You are welcome! A couple of logistical suggestions:
Could you please split up the series a bit and limit the next ser
On Fri, Apr 15, 2016 at 1:31 AM, Ingo Molnar wrote:
>
> * Kees Cook wrote:
>
>> From: Yinghai Lu
>>
>> Currently, the kernel run_size (size of code plus brk and bss) is
>> calculated via the shell script arch/x86/tools/calc_run_size.sh.
>> It gets the file offset and mem size of for the .bss and
* Kees Cook wrote:
> From: Yinghai Lu
>
> Currently, the kernel run_size (size of code plus brk and bss) is
> calculated via the shell script arch/x86/tools/calc_run_size.sh.
> It gets the file offset and mem size of for the .bss and .brk sections in
> vmlinux, and adds them as follows:
'of
From: Yinghai Lu
Currently, the kernel run_size (size of code plus brk and bss) is
calculated via the shell script arch/x86/tools/calc_run_size.sh. It gets
the file offset and mem size of for the .bss and .brk sections in vmlinux,
and adds them as follows:
run_size=$(( $offsetA + $sizeA + $sizeB
4 matches
Mail list logo
