It is a bug if there is a check for short reads
and that message doesn't get triggered.
There is a check for short reads .... the message isn't
being written out.
You are a complete idiot if you think that is not a bug.
POSIX compliance isn't the only standard of whether or not something is
a bug. If code is included to check for an error condition
(short reads), and DOES trigger in some cases, but not in others,
that is the essence of a bug in the code -- regardless of specs.
If you don't like my posts, Erik, you are free to ignore them.
Otherwise, stop adding off-topic comments like this:
Eric Blake wrote:
On 10/12/2012 09:25 AM, Linda Walsh wrote:
[please don't top-post on technical lists]
Hey guys, this is still a bug though:
Ishtar:dev/shm# dd if=4G of=4Ga bs=4G count=1
0+1 records in
0+1 records out
2147479552 bytes (2.1 GB) copied, 4.0274 s, 533 MB/s
(note no error message....)
Nope, that's not a bug, but behavior required by POSIX. You asked dd to
read _up to 4G_ for a count of exactly 1. Just because the read was
short does not make it an error
