Bug 591617 - lscpu does not use cpu masks properly
lscpu does not use cpu masks properly
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: util-linux-ng (Show other bugs)
6.1
All Linux
medium Severity medium
: rc
: ---
Assigned To: Karel Zak
Juraj Marko
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-12 13:35 EDT by Casey Dahlin
Modified: 2015-08-31 23:37 EDT (History)
6 users (show)

See Also:
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 16:52:22 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Casey Dahlin 2010-05-12 13:35:45 EDT
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 06:15:26 EDT
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 14:51:24 EDT
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 Product and Program Management 2010-06-28 11:43:08 EDT
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 16:52:22 EST
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.

Note You need to log in before you can comment on or make changes to this bug.