From: nigel@9fs.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bug in disk/format
Date: Mon, 27 May 2002 09:32:11 +0100 [thread overview]
Message-ID: <f713a44265e2b2f08f0db3807a60e79f@9fs.org> (raw)
> rsc writes:
>> For better or worse, the sd53c8xx driver
>> truncates very large writes (like an entire kernel!). It returns
>> the correct short write count, but format wasn't checking
>> for short writes.
>
> umm, isn't this a bug in the driver? the man page for write(2) says,
>
Yep, and I think "for better or worse" acknowledges that.
I fixed this over a year ago, but somehow it never made it to 3rd, and hence
not 4th, edition.
I've posted the fix to 9trouble, but anyone wanting to read/write more than
128K at a time to Symbios controlled disk can pick up the files as
http://www.9fs.org/dist/ncr/sd53c8xx.tgz
next reply other threads:[~2002-05-27 8:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-27 8:32 nigel [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-27 17:49 rsc
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=f713a44265e2b2f08f0db3807a60e79f@9fs.org \
--to=nigel@9fs.org \
--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).