Re: [PATCH v2] arm64: Fix for st->_stext_vmlinux not initialized when set VA_BITS_ACTUAL

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

 



On 2022/07/05 13:20, lijiang wrote:
> On Tue, Jul 5, 2022 at 10:10 AM HAGIO KAZUHITO(萩尾 一仁) <k-hagio-ab@xxxxxxx>
> wrote:
>>
>> On 2022/07/04 17:40, Qianli Zhao wrote:
>>> From: Qianli Zhao <qianli.zhao@xxxxxxxxxx>
>>>
>>> Setting st->_stext_vmlinux to UNINITIALIZED to search for "_stext"
>>> from the vmlinux. In the scenario where kaslr is disabled and
>>> without vmcore file, will get the wrong MODULES/VMALLOC ranges,
>>
>> Thanks for the update, probably s/vmcore file/vmcoreinfo/ is better,
>> but we will fix it.
>>
>> Acked-by: Kazuhito Hagio <k-hagio-ab@xxxxxxx>
>>
>> Lianbo, I think we can merge this first for the ramdump issue, but
> 
> 
> Sounds good, Kazu. For the v2: ACK.
> 
> is it better to look into the issue you found before merging this?
>>
>>
> Let's leave it there for now, and dig into the details later.

ok, applied this first.

https://github.com/crash-utility/crash/commit/6722ea102264b54529afc19d347a3a7473670fdd

Thanks,
Kazu
--
Crash-utility mailing list
Crash-utility@xxxxxxxxxx
https://listman.redhat.com/mailman/listinfo/crash-utility
Contribution Guidelines: https://github.com/crash-utility/crash/wiki




[Index of Archives]     [Fedora Development]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]

 

Powered by Linux