public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org,
	marado@student.dei.uc.pt
Subject: Re: grsecurity 2.1.0 release / 5 Linux kernel advisories (fwd)
Date: Fri, 7 Jan 2005 13:40:14 -0800	[thread overview]
Message-ID: <20050107134014.3ac297f3.akpm@osdl.org> (raw)
In-Reply-To: <4d8e3fd305010713032aeaa75c@mail.gmail.com>

Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com> wrote:
>
> the below email seems to be very intersting.

An unprivileged local user can DoS a Linux box to death with malloc and
memset, so the RLIMIT_MEMLOCK bug isn't particularly exceptional.  All the
others require root anyway.

I'll pass this on to appropriate people, see if we can get this all fixed
up, thanks.


  reply	other threads:[~2005-01-07 21:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-07 19:54 grsecurity 2.1.0 release / 5 Linux kernel advisories (fwd) Marcos D. Marado Torres
2005-01-07 21:03 ` Paolo Ciarrocchi
2005-01-07 21:40   ` Andrew Morton [this message]
2005-01-07 22:49     ` Alan Cox

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=20050107134014.3ac297f3.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marado@student.dei.uc.pt \
    --cc=paolo.ciarrocchi@gmail.com \
    --cc=torvalds@osdl.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