mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: "Zack Weinberg" <zackw@stanford.edu>
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: 2.2 PATCH: check return from copy_*_user in fs/pipe.c
Date: Wed, 20 Jun 2001 20:44:23 -0700 (PDT)	[thread overview]
Message-ID: <15153.28055.544280.527063@pizda.ninka.net> (raw)
In-Reply-To: <20010620202621.C12387@stanford.edu>
In-Reply-To: <20010620202621.C12387@stanford.edu>


Zack Weinberg writes:
 > Linus Torvalds wrote:
 > > And before you say "it has to return EFAULT", check the standards, and
 > > think about the case of libraries vs system calls - and how do you tell
 > > them apart?
 > 
 > My reading of the standard is that it has to either return EFAULT or
                                      ^^
 > raise SIGSEGV.  But I am not expert in XPG4-ese.

Linus is trying to point out: "what is this 'it'?"  Is it glibc or
what the kernel gives you?

 > Whether or not the standard requires anything, I would much rather
 > that the kernel not silently discard error conditions.

But only perhaps from a "quality of implementation" perspective not a
"correctness" one.

Later,
David S. Miller
davem@redhat.com


  reply	other threads:[~2001-06-21  3:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-21  3:26 Zack Weinberg
2001-06-21  3:44 ` David S. Miller [this message]
2001-06-21  6:10   ` Zack Weinberg
  -- strict thread matches above, loose matches on Subject: below --
2001-06-20  2:08 Zack Weinberg
2001-06-20  2:16 ` David S. Miller
2001-06-20  2:48   ` Zack Weinberg
2001-06-20  2:52   ` David S. Miller
2001-06-20  3:59     ` Zack Weinberg
2001-06-20  5:14       ` Linus Torvalds
2001-06-20  4:01     ` David S. Miller
2001-06-20  4:33 ` Andrew Tridgell
2001-06-20 15:52   ` Hugh Dickins

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=15153.28055.544280.527063@pizda.ninka.net \
    --to=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    --cc=zackw@stanford.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

all inboxes | Powered by JetHome®