Bug 591617

Summary: lscpu does not use cpu masks properly
Product: Red Hat Enterprise Linux 6 Reporter: Casey Dahlin <cdahlin>
Component: util-linux-ngAssignee: Karel Zak <kzak>
Status: CLOSED CURRENTRELEASE QA Contact: Juraj Marko <jmarko>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1CC: azelinka, james.leddy, jmarko, nlevinki, ovasik, vanhoof
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: util-linux-ng-2.17.2-4.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-10 21:52:22 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 Casey Dahlin 2010-05-12 17:35:45 UTC
lscpu does not correctly use cpu masks, which can lead to incorrect or confusing information reported.

http://article.gmane.org/gmane.linux.utilities.util-linux-ng/3180

Comment 1 Karel Zak 2010-06-14 10:15:26 UTC
The problem has been fixed in upstream tree. It's relatively invasive change. My suggestion is to rebase lscpu(1) in RHEL6.1.

Comment 2 James M. Leddy 2010-06-24 18:51:24 UTC
Can we rebase util-linux-ng in 6.0? The customer also wants the fsfreeze command:

http://thread.gmane.org/gmane.linux.utilities.util-linux-ng/3181/focus=3193

Comment 8 RHEL Program Management 2010-06-28 15:43:08 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 12 releng-rhel@redhat.com 2010-11-10 21:52:22 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.