From: Ralf Baechle <ralf@oss.sgi.com>
To: Carsten Langgaard <carstenl@mips.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: Insertion of die_if_kernel in unaligned.c
Date: Thu, 3 May 2001 14:21:14 -0300 [thread overview]
Message-ID: <20010503142114.A6081@bacchus.dhis.org> (raw)
In-Reply-To: <3AF13558.F26941EE@mips.com>; from carstenl@mips.com on Thu, May 03, 2001 at 12:39:20PM +0200
On Thu, May 03, 2001 at 12:39:20PM +0200, Carsten Langgaard wrote:
> In the latest version of arch/mips/kernel/unaligned.c, there has been
> inserted some calls to the die_if_kernel, which check if we are running
> in kernel mode and if so dies.
> I'm not so sure this is the right thing to do, the floating point
> emulator will in some cases generate an address error (e.g. if emulating
> a swc1 to an unaligned address). The result is that an user application
> can crash the kernel.
They're wrong and what's worse, I knew about them. The unaligned from
kernelspace case can also be triggered from the network stack so this
leaves machines open to remote DoS.
Ralf
prev parent reply other threads:[~2001-05-03 17:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-03 10:39 Insertion of die_if_kernel in unaligned.c Carsten Langgaard
2001-05-03 17:21 ` Ralf Baechle [this message]
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=20010503142114.A6081@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=carstenl@mips.com \
--cc=linux-mips@oss.sgi.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