public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Stephen Biggs" <s.biggs@softier.com>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bug in kernel code?
Date: Tue, 27 Aug 2002 21:29:06 -0700	[thread overview]
Message-ID: <3D6BEF22.21951.10E69E8@localhost> (raw)
In-Reply-To: <20020827.203946.102043898.davem@redhat.com>

On 27 Aug 2002 at 20:39, David S. Miller wrote:

>    How about (unsigned long)(~0)?
>    
> Realistically possible with any known configuration?
> 

You tell me.  You're saying a billion pages (((unsigned long)(~0)) >> 2) also crashes) is never 
going to be realistically possible?  Sounds like Bill Gates when he said (and I don't know the word-
for-word quote) "Who's ever going to need more than 640K??"  What if we get into 64 bit addressing? 
What if there is some sort of bug that passes all 1s on the stack for just this one instance?  
Never could "realistically" happen? Yeah, right; I've seen weirder things than that.

It's a question of mandatory paranoid sanity checking in an OS wherever possible.  Linux is trying 
to be known as robust.  Are you saying that a supposedly robust kernel should have a chance to 
crash in an infinite loop during initialization because there isn't code doing input validation 
when there isn't an optimization or speed issue?


  parent reply	other threads:[~2002-08-28  4:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3D6BB5C3.16057.2E515C@localhost>
     [not found] ` <20020827.172304.22017977.davem@redhat.com>
2002-08-28  0:32   ` Bug in kernel code? Stephen C. Biggs
2002-08-28  0:29     ` David S. Miller
2002-08-28  0:40       ` Stephen C. Biggs
2002-08-28  0:42         ` David S. Miller
2002-08-28  1:09           ` Stephen C. Biggs
2002-08-28  1:09             ` David S. Miller
2002-08-28  1:24               ` Stephen C. Biggs
2002-08-28  1:23                 ` David S. Miller
2002-08-28  2:42                   ` Stephen C. Biggs
2002-08-28  3:39                     ` David S. Miller
2002-08-28  3:57                       ` Luca Barbieri
2002-08-28  3:58                         ` David S. Miller
2002-08-28  4:10                           ` Luca Barbieri
2002-08-28  4:07                             ` David S. Miller
2002-08-28  4:29                               ` Luca Barbieri
2002-08-28  4:29                       ` Stephen Biggs [this message]
2002-08-28  4:26                         ` David S. Miller
2002-08-28 21:54                           ` H. Peter Anvin
2002-08-28  2:49                   ` Re[2]: " Stephen C. Biggs
2002-08-28  0:54   ` Stephen C. Biggs
2002-08-28  0:25 Stephen C. Biggs

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=3D6BEF22.21951.10E69E8@localhost \
    --to=s.biggs@softier.com \
    --cc=davem@redhat.com \
    --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