From: David Woodhouse <dwmw2@infradead.org>
To: Chris Evans <chris@scary.beasts.org>
Cc: kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org, davem@redhat.com
Subject: Re: SO_SNDTIMEO: 2.4 kernel bugs
Date: Tue, 20 Feb 2001 15:09:33 +0000 [thread overview]
Message-ID: <23164.982681773@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0102192146380.7008-100000@ferret.lmh.ox.ac.uk>
In-Reply-To: <Pine.LNX.4.30.0102192146380.7008-100000@ferret.lmh.ox.ac.uk>
chris@scary.beasts.org said:
> I think the proper fix, long term, is to fix our internal I/O routine
> APIs so that they are capable of returning a byte count _and_ an
> error. One day, that might be a useful thing to export to userspace.
The MTD code already does this.
--
dwmw2
next prev parent reply other threads:[~2001-02-20 15:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-17 1:35 SO_SNDTIMEO: 2.4 kernel bugs Chris Evans
2001-02-17 20:29 ` kuznet
2001-02-17 21:56 ` Chris Evans
2001-02-17 22:46 ` Chris Evans
2001-02-18 17:24 ` kuznet
2001-02-18 19:25 ` Chris Evans
2001-02-18 19:33 ` kuznet
2001-02-18 19:37 ` Chris Evans
2001-02-18 19:48 ` kuznet
2001-02-19 1:04 ` Chris Evans
2001-02-19 1:43 ` sendfile() breakage was " Chris Evans
2001-02-19 18:03 ` kuznet
2001-02-19 21:56 ` Chris Evans
2001-02-20 15:09 ` David Woodhouse [this message]
2001-02-18 1:50 ` Chris Evans
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=23164.982681773@redhat.com \
--to=dwmw2@infradead.org \
--cc=chris@scary.beasts.org \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
/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