From: rsc@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bug in disk/format
Date: Mon, 27 May 2002 13:49:30 -0400 [thread overview]
Message-ID: <fe369894ea709839e626f4382450ad30@plan9.bell-labs.com> (raw)
> umm, isn't this a bug in the driver? the man page for write(2) says,
>
> The number of characters actually written is returned.
> It should be regarded as an error if this is not the same as requested.
>
> so yes, disk/format should check for short writes, but it should fail
> with a write error if it gets one, no?
and indeed it does, now. it also only tries to write 8k
at a time to avoid aggravating the sd53c8xx problem.
> question, if it is an error, should errstr() be set?
it won't be, because the system call didn't return -1.
not sure whether it should be.
russ
next reply other threads:[~2002-05-27 17:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-27 17:49 rsc [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-27 8:32 nigel
2002-05-26 22:13 rsc
2002-05-27 6:31 ` Michael Baldwin
2002-05-26 6:19 rsc
2002-05-26 20:40 ` Mike Haertel
2002-05-26 5:27 rsc
2002-05-26 6:01 ` Mike Haertel
2002-05-26 5:22 Geoff Collyer
2002-05-26 4:13 rsc
2002-05-26 5:11 ` Mike Haertel
2002-05-26 3:01 Mike Haertel
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=fe369894ea709839e626f4382450ad30@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--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).