mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: linux-kernel@vger.kernel.org
Cc: Robert Williamson <robbiew@us.ibm.com>, Paul Larson <plars@us.ibm.com>
Subject: Re: [ANNOUNCE] Linux Test Project October Release Available
Date: Wed, 9 Oct 2002 13:39:01 +0200	[thread overview]
Message-ID: <20021009133901.T642@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <3DA33BF1.3F43E5C0@digeo.com>; from akpm@digeo.com on Tue, Oct 08, 2002 at 01:11:29PM -0700

On Tue, Oct 08, 2002 at 01:11:29PM -0700, Andrew Morton wrote:
> Robert Williamson wrote:
> > 
> > ...
> > - Fix for "writev01" to check for EINVAL on      ( Paul Larson )
> >   2.5.35 and above kernels
> > 
> 
> whoa.  I've been asleep.  The 2.4 kernel _does_ return zero
> if passed a zero segment count.
> 
> So we need to fix 2.5 to do that as well.  Sure, the spec
> appears to allow either, but given that, we should preserve
> the 2.4 behaviour.

I agree. Passing zero counts means "no work to do" and passing
that information is never a problem in any function.

The same goes for a segment with zero len (which is a way to
measure user space to kernel driver latency, if the driver
implements writev and readv).

It's only a "performance bug", if that is used in a real
application, no wrong parameters.

Regards

Ingo Oeser
-- 
Science is what we can tell a computer. Art is everything else. --- D.E.Knuth

      reply	other threads:[~2002-10-09 16:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-08 19:37 Robert Williamson
2002-10-08 20:11 ` Andrew Morton
2002-10-09 11:39   ` Ingo Oeser [this message]

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=20021009133901.T642@nightmaster.csn.tu-chemnitz.de \
    --to=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=plars@us.ibm.com \
    --cc=robbiew@us.ibm.com \
    /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

all inboxes | Powered by JetHome®