The panic_print setting allows users to collect more information in a
panic event, like memory stats, tasks, CPUs backtraces, etc.
This is a pretty interesting debug mechanism, but currently the print
event happens *after* kmsg_dump(), meaning that Pstore, for example,
cannot collect a dmesg with
On 2021/12/30 18:40, Borislav Petkov wrote:
> On Thu, Dec 30, 2021 at 06:14:59PM +0800, Leizhen (ThunderTown) wrote:
>>
>> Hi, Dave, Baoquan, Borislav:
>> What do you think about the introduction of parse_crashkernel_high_low()?
>> If everyone
>> doesn't object, I'll bring it to the next
On Thu, Dec 30, 2021 at 06:14:59PM +0800, Leizhen (ThunderTown) wrote:
>
> Hi, Dave, Baoquan, Borislav:
> What do you think about the introduction of parse_crashkernel_high_low()?
> If everyone
> doesn't object, I'll bring it to the next version. But I'll make some
> adjustments to the
>
Hi, Dave, Baoquan, Borislav:
What do you think about the introduction of parse_crashkernel_high_low()? If
everyone
doesn't object, I'll bring it to the next version. But I'll make some
adjustments to the
patches, see below. If there's any objection, I still strongly recommend
removing the
On 2021/12/30 10:39, Leizhen (ThunderTown) wrote:
>
>
> On 2021/12/30 0:51, Borislav Petkov wrote:
>> On Wed, Dec 29, 2021 at 11:04:21PM +0800, Leizhen (ThunderTown) wrote:
>>> Chen Zhou and I tried to share the code because of a suggestion. After so
>>> many
>>> attempts, it doesn't seem to
Fix a spelling mistake sizez -> size, to remove some warnings
found by running scripts/kernel-doc, which is caused by using
'make W=1'.
fs/proc/vmcore.c:489: warning: Function parameter or member 'size' not
described in 'vmcore_alloc_buf'
fs/proc/vmcore.c:489: warning: Excess function parameter
