Dave Anderson wrote:
>>>>>> So my initial leaning would be to continue to show what's actually there.
>>>>>> I trust myself as a crash analyzer more than I trust the administrator.
>>>>>> But I could be convinced otherwise.
>>>>>> What do others on the list think about this?
>>>> I would much rather see all of the contents of the log buffer.
>> OK, I attach a new patch for outputing all of the contents of the log
>> buffer. How about this patch ?
> It appears to works OK, although the leftover references to "logged_chars"
> should be removed from your patch, correct?
Yes, you are right. "logged_chars" is not referred by my patch,
and it should be removed. This is a new patch for removing it.
[Patch-v3] Fix handling the ring buffer for 'log' command.
Changelog of v3:
- Removing the references to "logged_chars".
Changelog of v2:
- Extending the output range of 'log' command to all the ring buffer.
I found there is a 'log' command problem related to handling the ring
buffer, and this patch fixes it.
The ring buffer can be cleared by klogctl(2) from a user process, but
current crash utility does not consider this case. The following output
of current crash utility is example of this case. You see there are some
messages after the panic message. These messages are the oldest log data,
so they should be output first.