mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Adams <cmadams@hiwaay.net>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.19-rc1 broke OSF binaries on alpha
Date: Fri, 28 Jun 2002 23:39:06 -0500	[thread overview]
Message-ID: <20020628233906.A236282@hiwaay.net> (raw)

Once upon a time, Ivan Kokshaysky  <ink@jurassic.park.msu.ru> said:
>IIRC, the problem is that BSD and OSF readv/writev(2) manuals
>explicitly talked of 32 bit iov_len, thus allowing the application
>to pass junk in an upper half of the 64 bit word.
>This change broke widely used netscape and acrobat reader,
>please revert it until we have a better solution:

The Tru64 4.0G and 5.1A man pages say that if the sum of the iov_len
values is negative or overflows a 32 bit integer that EINVAL will be
returned, but I think this is only for the backwards compatible
interface where iov_len was defined as int.  It is now defined as size_t
and the rest of the man page never says anything about a 32 bit iov_len
and the upper half being ignored.
-- 
Chris Adams <cmadams@hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.

             reply	other threads:[~2002-06-29  4:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-29  4:39 Chris Adams [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-28 10:54 Ivan Kokshaysky
2002-06-28 20:31 ` Marcelo Tosatti
2002-06-29  2:28   ` Alan Cox
2002-06-29 23:50     ` Ivan Kokshaysky
2002-07-01  7:54       ` Kurt Garloff
2002-07-01 16:17         ` Jeff Garzik
2002-07-01 13:03       ` jlnance
2002-07-01 14:02         ` Ivan Kokshaysky
2002-07-01 19:40           ` Måns Rullgård
2002-07-02 15:05             ` Ivan Kokshaysky
2002-07-02 23:13               ` Richard Henderson
2002-07-03  0:31                 ` Ivan Kokshaysky
2002-06-29  2:26 ` Alan Cox
2002-06-29 22:45   ` Ivan Kokshaysky
2002-07-02 20:56     ` Marcelo Tosatti

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=20020628233906.A236282@hiwaay.net \
    --to=cmadams@hiwaay.net \
    --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

all inboxes | Powered by JetHome®