Bug 1928389

Summary:	log -m shows log level and priority; should only show level
Product:	Red Hat Enterprise Linux 8	Reporter:	John Pittman <jpittman>
Component:	crash	Assignee:	ltao
Status:	CLOSED ERRATA	QA Contact:	Ruowen Qin <ruqin>
Severity:	medium	Docs Contact:	Sujata Kurup <skurup>
Priority:	high
Version:	8.2	CC:	lijiang, ruqin, ruyang, skurup, xiawu
Target Milestone:	rc	Keywords:	FutureFeature, Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	crash-7.3.0-2.el8	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-11-09 18:08:37 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description John Pittman 2021-02-13 16:19:28 UTC

Description of problem:

log -m shows log level and priority; should only show level

[  394.372139] <82> blk_mq_flush_plug_list+0x196/0x2c0
[  394.372154] <82> ? __sbitmap_queue_get+0x24/0x90
[  394.372168] <82> blk_flush_plug_list+0xd7/0x100
[  394.372181] <82> blk_mq_make_request+0x258/0x5d0
[  394.372196] <82> generic_make_request+0xcf/0x310

Version-Release number of selected component (if applicable):

crash-7.2.7-3.el8.x86_64

How reproducible:

Every time

Steps to Reproduce:

Run log -m on vmcore

Actual results:

The log -m command will show the log level and the log priority.

Expected results:

The log priority should be stripped off and only the level shown.

Additional info:

Potential patch submitted at https://listman.redhat.com/archives/crash-utility/2021-February/msg00010.html

Comment 1 John Pittman 2021-02-18 16:06:12 UTC

V2 sent: https://listman.redhat.com/archives/crash-utility/2021-February/msg00013.html

Comment 11 errata-xmlrpc 2021-11-09 18:08:37 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (crash bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:4199