mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Larson <plars@austin.ibm.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] vfs_read/vfs_write small bug fix (2.5.29)
Date: 29 Jul 2002 17:06:18 -0500	[thread overview]
Message-ID: <1027980379.11135.223.camel@plars.austin.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0207291418280.1470-100000@penguin.transmeta.com>

On Mon, 2002-07-29 at 16:22, Linus Torvalds wrote:
> Does this work for you? If not, that implies that glibc may be missing a
> 
> 	if (pos < 0) {
> 		errno = EINVAL;
> 		return -1;
> 	}
> 
> in its implementation of the pread/pwrite shim layer.
> 
> (Or maybe glibc doesn't know that the kernel pread/pwrite system calls 
> were always 64-bit clean, and it just happened to work).
> 
> 		Linus
No, with just this patch it still fails on pread02 and pwrite02.

# ./pread02
pread02     1  PASS  :  pread() fails, file descriptor is a PIPE or
FIFO, errno:29
pread02     2  FAIL  :  pread() returned 0, expected -1, errno:22

# ./pwrite02
pwrite02    1  PASS  :  file descriptor is a PIPE or FIFO, errno:29
caught SIGXFSZ
pwrite02    2  FAIL  :  specified offset is -ve or invalid, unexpected
errno:27, expected:22
pwrite02    3  PASS  :  file descriptor is bad, errno:9

Paul Larson
Linux Test Project
http://ltp.sourceforge.net


  reply	other threads:[~2002-07-29 22:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-29 18:25 Badari Pulavarty
2002-07-29 19:02 ` Paul Larson
2002-07-29 20:11 ` Linus Torvalds
2002-07-29 21:06   ` Paul Larson
2002-07-29 21:22     ` Linus Torvalds
2002-07-29 22:06       ` Paul Larson [this message]
2002-07-29 22:17         ` Linus Torvalds
2002-07-30  7:37           ` Andreas Schwab

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=1027980379.11135.223.camel@plars.austin.ibm.com \
    --to=plars@austin.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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®