Bug 705128 - blkparse uses the wrong variable when printing out PC Writes Compl
Summary: blkparse uses the wrong variable when printing out PC Writes Compl
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: blktrace
Version: 6.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Eric Sandeen
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On: 711344
Blocks: 743047
TreeView+ depends on / blocked
 
Reported: 2011-05-16 18:29 UTC by Jeff Moyer
Modified: 2011-12-06 19:04 UTC (History)
2 users (show)

Fixed In Version: blktrace-1.0.1-5.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 19:04:54 UTC
Target Upstream Version:

Attachments (Terms of Use)
fix the pc writes output in blkparse (720 bytes, text/plain)
2011-05-16 18:29 UTC, Jeff Moyer 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1758 0 normal SHIPPED_LIVE blktrace bug fix and enhancement update 2011-12-06 01:01:41 UTC

Description Jeff Moyer 2011-05-16 18:29:02 UTC 
Created attachment 499208 [details]
fix the pc writes output in blkparse

Description of problem:
In some traces, I noticed that pc writes completed was equal to the number of fs writes completed, even there were no pc writes issued.  The problem was a pretty obvious typo in the blkparse code.
Comment 2 Eric Sandeen 2011-05-16 18:51:25 UTC 
http://marc.info/?l=linux-btrace&m=130557019213194&w=2

Thanks Jeff!
Comment 7 Eric Sandeen 2011-07-22 21:07:36 UTC 
I checked this in but the build is failing off in TeX land.  No idea what's wrong, it builds fine locally on a rhel6 box...
Comment 11 Eric Sandeen 2011-08-03 16:17:35 UTC 
Committed upstream now:

http://git.kernel.dk/?p=blktrace.git;a=commitdiff;h=d0576a3a885b1b5fc6a47c35d9537d9717444238
Comment 17 errata-xmlrpc 2011-12-06 19:04:54 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, and where to find the updated
files, follow the link below.

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

http://rhn.redhat.com/errata/RHBA-2011-1758.html
Note You need to log in before you can comment on or make changes to this bug.