Bug 491508

Summary:	"Utrace:" line in /proc/$pid/status has unusual format, breaks parsing in yum
Product:	[Fedora] Fedora	Reporter:	Michal Schmidt <mschmidt>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	rawhide	CC:	kernel-maint, quintela, roland, selinux
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	kernel-2.6.29-0.279.rc8.git6.fc11	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-03-24 09:11:09 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Michal Schmidt 2009-03-22 10:46:50 UTC

Description of problem:
All lines in /proc/$pid/status use a colon and a tab to separate the key from value(s). The only exception in the "Utrace: " line which uses a space instead of the tab.
This breaks yum's show_lock_owner function which parses this file and expects the key/value separator to be ':\t'.
yum could be made more robust here, but it's better if the kernel keeps the format of the lines consistent, because who knows what other software may have the same expectation.

Version-Release number of selected component (if applicable):
kernel-2.6.29-0.267.rc8.git4.fc11.x86_64

How reproducible:
always

Steps to Reproduce:
1. Look at /proc/self/status with a hex editor
2. See the "Utrace: " line.
  
Actual results:
The character after the colon is a space (0x20).

Expected results:
The character after the colon should be a tab (0x9).

Additional information:
The faulty line is printed in kernel/utrace.c:task_utrace_proc_status(), it comes from linux-2.6-utrace.patch.

Comment 1 Roland McGrath 2009-03-23 02:27:37 UTC

Should be fixed in the next rawhide kernel build.

Comment 2 Michal Schmidt 2009-03-23 17:17:20 UTC

*** Bug 491482 has been marked as a duplicate of this bug. ***

Comment 3 Michal Schmidt 2009-03-24 09:11:09 UTC

It works now. Thanks.