From: Greg KH <gregkh@linuxfoundation.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: elena.reshetova@intel.com, keescook@chromium.org, arnd@arndb.de,
tglx@linutronix.de, mingo@kernel.org, h.peter.anvin@intel.com,
will.deacon@arm.com, dwindsor@gmail.com, dhowells@redhat.com,
linux-kernel@vger.kernel.org,
kernel-hardening@lists.openwall.com
Subject: [kernel-hardening] Re: [PATCH 2/5] kref: Implement using refcount_t
Date: Mon, 6 Feb 2017 14:06:23 +0100 [thread overview]
Message-ID: <20170206130623.GA5869@kroah.com> (raw)
In-Reply-To: <20170203132737.365388918@infradead.org>
On Fri, Feb 03, 2017 at 02:26:00PM +0100, Peter Zijlstra wrote:
> Use the refcount_t 'atomic' type to implement kref, this makes kref
> more robust by bringing saturation semantics.
>
> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: elena.reshetova@intel.com, keescook@chromium.org, arnd@arndb.de,
tglx@linutronix.de, mingo@kernel.org, h.peter.anvin@intel.com,
will.deacon@arm.com, dwindsor@gmail.com, dhowells@redhat.com,
linux-kernel@vger.kernel.org,
kernel-hardening@lists.openwall.com
Subject: Re: [PATCH 2/5] kref: Implement using refcount_t
Date: Mon, 6 Feb 2017 14:06:23 +0100 [thread overview]
Message-ID: <20170206130623.GA5869@kroah.com> (raw)
In-Reply-To: <20170203132737.365388918@infradead.org>
On Fri, Feb 03, 2017 at 02:26:00PM +0100, Peter Zijlstra wrote:
> Use the refcount_t 'atomic' type to implement kref, this makes kref
> more robust by bringing saturation semantics.
>
> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2017-02-06 13:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 13:25 [kernel-hardening] [PATCH 0/5] refcount_t and various related bits Peter Zijlstra
2017-02-03 13:25 ` Peter Zijlstra
2017-02-03 13:25 ` [kernel-hardening] [PATCH 1/5] refcount_t: A special purpose refcount type Peter Zijlstra
2017-02-03 13:25 ` Peter Zijlstra
2017-02-03 18:09 ` [kernel-hardening] " Kees Cook
2017-02-03 18:09 ` Kees Cook
2017-02-03 23:37 ` [kernel-hardening] " Kees Cook
2017-02-03 23:37 ` Kees Cook
2017-02-03 13:26 ` [kernel-hardening] [PATCH 2/5] kref: Implement using refcount_t Peter Zijlstra
2017-02-03 13:26 ` Peter Zijlstra
2017-02-06 13:06 ` Greg KH [this message]
2017-02-06 13:06 ` Greg KH
2017-02-03 13:26 ` [kernel-hardening] [PATCH 3/5] x86: Implement __WARN using UD2 Peter Zijlstra
2017-02-03 13:26 ` Peter Zijlstra
2017-02-03 13:26 ` [kernel-hardening] [PATCH 4/5] atomic: Introduce atomic_try_cmpxchg() Peter Zijlstra
2017-02-03 13:26 ` Peter Zijlstra
2017-02-06 4:24 ` [kernel-hardening] " Boqun Feng
2017-02-06 4:24 ` Boqun Feng
2017-02-06 6:32 ` [kernel-hardening] " Boqun Feng
2017-02-06 6:32 ` Boqun Feng
2017-02-06 8:12 ` [kernel-hardening] " Peter Zijlstra
2017-02-06 8:12 ` Peter Zijlstra
2017-02-03 13:26 ` [kernel-hardening] [PATCH 5/5] refcount: Use atomic_try_cmpxchg() Peter Zijlstra
2017-02-03 13:26 ` Peter Zijlstra
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=20170206130623.GA5869@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=dhowells@redhat.com \
--cc=dwindsor@gmail.com \
--cc=elena.reshetova@intel.com \
--cc=h.peter.anvin@intel.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.