From: "David S. Miller" <davem@davemloft.net>
To: herbert@gondor.apana.org.au
Cc: jesper.juhl@gmail.com, mru@inprovide.com, rommer@active.by,
bernd@firmix.at, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: udp.c
Date: Mon, 13 Jun 2005 16:20:52 -0700 (PDT) [thread overview]
Message-ID: <20050613.162052.41635836.davem@davemloft.net> (raw)
In-Reply-To: <20050613230422.GA7269@gondor.apana.org.au>
From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Tue, 14 Jun 2005 09:04:22 +1000
> On Mon, Jun 13, 2005 at 02:57:16PM -0700, David S. Miller wrote:
> > From: Herbert Xu <herbert@gondor.apana.org.au>
> > Date: Tue, 14 Jun 2005 07:42:52 +1000
> >
> > > It'll dump the stack anyway if we just make it a NULL pointer.
> >
> > Some platforms don't handle that very cleanly, for example
> > it may be necessary to have something mapped at page zero
> > for one reason or another.
>
> Are there any existing platforms that do that in kernel mode?
X86 did, especially during bootup, for a long time.
I know the highly optimized sparc64 instruction TLB miss handler
doesn't handle this properly and this usually hangs the machine.
I've put some checks in there that tries to handle it properly,
but there are still some cases that pass through.
next prev parent reply other threads:[~2005-06-13 23:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050613.124515.104034144.davem@davemloft.net>
2005-06-13 21:42 ` udp.c Herbert Xu
2005-06-13 21:57 ` udp.c David S. Miller
2005-06-13 23:04 ` udp.c Herbert Xu
2005-06-13 23:20 ` David S. Miller [this message]
2005-06-13 23:53 ` udp.c Andi Kleen
2005-06-14 0:00 ` udp.c David S. Miller
2005-06-14 0:12 ` udp.c Andi Kleen
2005-06-14 1:11 ` udp.c David S. Miller
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=20050613.162052.41635836.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bernd@firmix.at \
--cc=herbert@gondor.apana.org.au \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mru@inprovide.com \
--cc=netdev@vger.kernel.org \
--cc=rommer@active.by \
/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;
as well as URLs for NNTP newsgroup(s).