From: Mateusz Guzik <mguzik@redhat.com>
To: Lionel Debroux <lionel_debroux@yahoo.fr>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] drm: make variable named "refcount" atomic, like most refcounts in the kernel.
Date: Sat, 26 Apr 2014 19:03:06 +0200 [thread overview]
Message-ID: <20140426170305.GA17562@mguzik.redhat.com> (raw)
In-Reply-To: <248367.21250.bm@smtp144.mail.ir2.yahoo.com>
On Sat, Apr 26, 2014 at 06:06:15PM +0200, Lionel Debroux wrote:
> Based on PaX.
>
> ---
>
> From 7c712cadd97d43d03ff3d7ca04fd85bd8c6eb34a Mon Sep 17 00:00:00 2001
> From: Lionel Debroux <lionel_debroux@yahoo.fr>
> Date: Sat, 26 Apr 2014 15:53:55 +0200
> Subject: drm: make variable named "refcount" atomic, like most refcounts in
> the kernel.
>
> Extracted from the PaX patch.
>
>
[snip]
> mutex_lock(&item->mutex);
> - BUG_ON(item->refcount == 0);
> + BUG_ON(atomic_read(&item->refcount) == 0);
> BUG_ON(ref->object != item->object);
> - if (--item->refcount == 0) {
> + if (atomic_dec_and_test(&item->refcount)) {
> ref->release(ref);
> item->object = NULL;
> }
I believe this change is in grsecurity so that overflow detector can be
used, there is clearly no reason to use mere atomic ops.
It may be that kernel devs would accept a patch implementing generic
refcount manipulation primitives without atomicity guarantees, which
could be used in cases like this.
Then atomic and non-atomic versions could be used to detect overflows and
overputs at least in debug kernels.
--
Mateusz Guzik
next prev parent reply other threads:[~2014-04-26 17:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-26 16:06 [PATCH] drm: make variable named "refcount" atomic, like most refcounts in the kernel Lionel Debroux
2014-04-26 16:35 ` Al Viro
2014-04-26 17:03 ` Mateusz Guzik [this message]
2014-04-26 20:09 ` Lionel Debroux
2014-04-26 23:00 ` Al Viro
2014-04-26 23:42 ` Mateusz Guzik
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=20140426170305.GA17562@mguzik.redhat.com \
--to=mguzik@redhat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lionel_debroux@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox