From: Mike Haertel <mike@ducky.net>
To: 9fans@cse.psu.edu
Subject: [9fans] minor bug in dd + fix
Date: Sun, 26 May 2002 16:07:23 -0700 [thread overview]
Message-ID: <200205262307.g4QN7N9w000378@ducky.net> (raw)
While looking into the disk/format bug, I noticed that dd is
printing incorrect counts of blocks written. The reason is
that it is incrementing the count of blocks written before it
actually checks to see if the write succeeded.
Here's a fix:
term% diff dd.c.old dd.c
293,295d292
< if(obc == obs)
< nofr++; else
< nopr++;
297a295,296
> if (c > 0)
> ++nopr;
300a300,303
> if(obc == obs)
> nofr++;
> else
> nopr++;
reply other threads:[~2002-05-26 23:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200205262307.g4QN7N9w000378@ducky.net \
--to=mike@ducky.net \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).