From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andrew Morton <akpm@osdl.org>
Cc: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>,
torvalds@osdl.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
marado@student.dei.uc.pt
Subject: Re: grsecurity 2.1.0 release / 5 Linux kernel advisories (fwd)
Date: Fri, 07 Jan 2005 22:49:15 +0000 [thread overview]
Message-ID: <1105136300.7628.8.camel@localhost.localdomain> (raw)
In-Reply-To: <20050107134014.3ac297f3.akpm@osdl.org>
On Gwe, 2005-01-07 at 21:40, Andrew Morton wrote:
> 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.
The moxa one is insufficient too.
All in -ac7 just brewing now
prev parent reply other threads:[~2005-01-07 23:57 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
2005-01-07 22:49 ` Alan Cox [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=1105136300.7628.8.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=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;
as well as URLs for NNTP newsgroup(s).