All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wedgwood <cw@f00f.org>
To: Jamie Lokier <lk@tantalophile.demon.co.uk>
Cc: Kurt Roeckx <Q@ping.be>, Russell King <rmk@arm.linux.org.uk>,
	Vadim Lebedev <vlebedev@aplio.fr>,
	linux-kernel@vger.kernel.org
Subject: Re: Potenitial security hole in the kernel
Date: Tue, 29 May 2001 19:35:40 +1200	[thread overview]
Message-ID: <20010529193540.A7029@metastasis.f00f.org> (raw)
In-Reply-To: <003601c0e7bf$41953080$0101a8c0@LAP> <20010529001256.F9203@flint.arm.linux.org.uk> <20010529013030.A3381@ping.be> <20010529014635.A3499@ping.be> <20010529023222.C6061@pcep-jamie.cern.ch>
In-Reply-To: <20010529023222.C6061@pcep-jamie.cern.ch>; from lk@tantalophile.demon.co.uk on Tue, May 29, 2001 at 02:32:23AM +0200

On Tue, May 29, 2001 at 02:32:23AM +0200, Jamie Lokier wrote:

    By the way, the context stored on the stack is entirely a user
    space context, however it does include some information from the
    kernel that may be useful to user space, such as a page fault
    address.

I actually (ab)used this for userspace paging with mprotect and
friends.... nasty hack :)



  --cw

  reply	other threads:[~2001-05-29  8:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-28 21:43 Potenitial security hole in the kernel Vadim Lebedev
2001-05-28 22:21 ` Philip Blundell
2001-05-28 22:26   ` Vadim Lebedev
2001-05-28 22:29 ` Kurt Roeckx
2001-05-28 22:30   ` Vadim Lebedev
2001-05-28 23:15     ` Kurt Roeckx
2001-05-28 22:44 ` Brett Frankenberger
2001-05-28 23:12 ` Russell King
2001-05-28 23:30   ` Kurt Roeckx
2001-05-28 23:46     ` Kurt Roeckx
2001-05-29  0:32       ` Jamie Lokier
2001-05-29  7:35         ` Chris Wedgwood [this message]
2001-05-29 10:14           ` Jamie Lokier

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=20010529193540.A7029@metastasis.f00f.org \
    --to=cw@f00f.org \
    --cc=Q@ping.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lk@tantalophile.demon.co.uk \
    --cc=rmk@arm.linux.org.uk \
    --cc=vlebedev@aplio.fr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.