From: "PaX Team" <pageexec@freemail.hu>
To: Greg KH <gregkh@linuxfoundation.org>, David Windsor <dwindsor@gmail.com>
Cc: Roland Dreier <roland@purestorage.com>,
Djalal Harouni <tixxdz@opendz.org>,
Vasiliy Kulikov <segoon@openwall.com>,
kernel-hardening@lists.openwall.com,
Kees Cook <keescook@chromium.org>,
Ubuntu security discussion <ubuntu-hardened@lists.ubuntu.com>,
linux-kernel@vger.kernel.org, spender@grsecurity.net
Subject: Re: [kernel-hardening] Re: Add overflow protection to kref
Date: Sat, 25 Feb 2012 00:14:43 +0200 [thread overview]
Message-ID: <4F4819E3.23795.217CF269@pageexec.freemail.hu> (raw)
In-Reply-To: <CAEXv5_jEW6EA6nOd6pMJbh6PTd=+piHqzNA8Fb+gt2VGroba0A@mail.gmail.com>
On 24 Feb 2012 at 14:04, David Windsor wrote:
> Suggestions on recovering from an overflow here?
do what PaX does? :)
1. saturate the refcount
2. report the event (pax_report_refcount_overflow)
3. kill the triggering userland process (this may be optional but it's a good measure
if you have stuff like grsecurity's lockout feature)
> 2. Detect the overflow before it happens, don't increment the counter,
> issue a warning but no BUG.
> This could also lead to some "undefined" behavior in subsystems.
it's called a memory leak :).
prev parent reply other threads:[~2012-02-24 23:15 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEXv5_gkTsPHDFh+wQqD3P3D-Z+uCN-_1bVyHfHV=u7bS-tgeA@mail.gmail.com>
2012-02-16 20:45 ` Kees Cook
2012-02-17 0:24 ` Greg Kroah-Hartman
2012-02-17 1:06 ` Kees Cook
2012-02-17 1:40 ` Greg KH
2012-02-17 2:11 ` [ubuntu-hardened] " Kees Cook
2012-02-17 2:48 ` David Windsor
2012-02-17 3:32 ` Greg KH
2012-02-17 6:33 ` Alexey Dobriyan
2012-02-17 13:23 ` pageexec
2012-02-17 7:59 ` [kernel-hardening] " Vasiliy Kulikov
2012-02-17 17:53 ` Greg KH
2012-02-17 17:54 ` Greg KH
2012-02-17 19:37 ` Vasiliy Kulikov
2012-02-17 23:39 ` Djalal Harouni
2012-02-18 1:44 ` Roland Dreier
2012-02-18 16:15 ` David Windsor
2012-02-18 16:35 ` Vasiliy Kulikov
2012-02-18 16:18 ` Greg KH
2012-02-24 17:58 ` David Windsor
2012-02-24 18:37 ` Greg KH
2012-02-24 18:52 ` Kees Cook
2012-02-24 19:05 ` Nick Bowler
2012-02-24 19:13 ` Vasiliy Kulikov
2012-02-24 19:35 ` Nick Bowler
2012-02-24 21:59 ` PaX Team
2012-02-24 18:58 ` Vasiliy Kulikov
2012-02-24 19:41 ` Greg KH
2012-02-24 20:04 ` Kees Cook
2012-02-24 19:04 ` David Windsor
2012-02-24 22:14 ` PaX Team [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=4F4819E3.23795.217CF269@pageexec.freemail.hu \
--to=pageexec@freemail.hu \
--cc=dwindsor@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@purestorage.com \
--cc=segoon@openwall.com \
--cc=spender@grsecurity.net \
--cc=tixxdz@opendz.org \
--cc=ubuntu-hardened@lists.ubuntu.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
Powered by JetHome