From: Elena Reshetova <elena.reshetova@intel.com>
To: linux-kernel@vger.kernel.org
Cc: peterz@infradead.org, gregkh@linuxfoundation.org,
akpm@linux-foundation.org, ebiederm@xmission.com,
mingo@redhat.com, adobriyan@gmail.com, serge@hallyn.com,
arozansk@redhat.com, dave@stgolabs.net, keescook@chromium.org,
Elena Reshetova <elena.reshetova@intel.com>
Subject: [PATCH 0/3] v2 ipc subsystem refcount coversions
Date: Fri, 7 Jul 2017 11:59:49 +0300 [thread overview]
Message-ID: <1499417992-3238-1-git-send-email-elena.reshetova@intel.com> (raw)
Changes in v2:
* add a new patch on kern_ipc_perm.refcount
* drop the patch on ipc_rcu.refcount
* rebase on top of linux-next/master
* Now by default refcount_t = atomic_t (*) and uses all atomic
standard operations unless CONFIG_REFCOUNT_FULL is enabled.
This is a compromise for the systems that are critical on
performance (such as net) and cannot accept even slight delay
on the refcounter operations.
This series, for ipc subsystem components, replaces atomic_t reference
counters with the new refcount_t type and API (see include/linux/refcount.h).
By doing this we prevent intentional or accidental
underflows or overflows that can led to use-after-free vulnerabilities.
The patches are fully independent and can be cherry-picked separately.
If there are no objections to the patches, please merge them via respective trees.
* The respective change is currently merged into -next as
"locking/refcount: Create unchecked atomic_t implementation".
Elena Reshetova (3):
ipc: convert ipc_namespace.count from atomic_t to refcount_t
ipc: convert sem_undo_list.refcnt from atomic_t to refcount_t
ipc: convert kern_ipc_perm.refcount from atomic_t to refcount_t
include/linux/ipc.h | 3 ++-
include/linux/ipc_namespace.h | 5 +++--
ipc/msgutil.c | 2 +-
ipc/namespace.c | 4 ++--
ipc/sem.c | 8 ++++----
ipc/util.c | 6 +++---
6 files changed, 15 insertions(+), 13 deletions(-)
--
2.7.4
next reply other threads:[~2017-07-07 9:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 8:59 Elena Reshetova [this message]
2017-07-07 8:59 ` [PATCH 1/3] ipc: convert ipc_namespace.count from atomic_t to refcount_t Elena Reshetova
2017-07-09 21:59 ` Eric W. Biederman
2017-07-10 6:48 ` Reshetova, Elena
2017-07-10 8:37 ` Eric W. Biederman
2017-07-10 9:34 ` Alexey Dobriyan
2017-07-10 11:19 ` Eric W. Biederman
2017-07-10 9:56 ` Reshetova, Elena
2017-07-10 11:26 ` Eric W. Biederman
2017-07-10 12:11 ` Reshetova, Elena
2017-07-10 20:32 ` Eric W. Biederman
2017-07-12 9:21 ` Reshetova, Elena
2017-07-19 22:35 ` Andrew Morton
2017-07-19 22:54 ` Davidlohr Bueso
2017-07-19 22:58 ` Andrew Morton
2017-07-19 23:11 ` Davidlohr Bueso
2017-07-19 23:20 ` Kees Cook
2017-07-20 0:32 ` Kees Cook
2017-07-20 9:34 ` Ingo Molnar
2017-07-20 12:34 ` Eric W. Biederman
2017-07-20 15:12 ` Kees Cook
2017-07-07 8:59 ` [PATCH 2/3] ipc: convert sem_undo_list.refcnt " Elena Reshetova
2017-07-07 8:59 ` [PATCH 3/3] ipc: convert kern_ipc_perm.refcount " Elena Reshetova
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=1499417992-3238-1-git-send-email-elena.reshetova@intel.com \
--to=elena.reshetova@intel.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arozansk@redhat.com \
--cc=dave@stgolabs.net \
--cc=ebiederm@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=serge@hallyn.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
all inboxes | Powered by JetHome®