From: Kees Cook <keescook@chromium.org>
To: Will Deacon <will@kernel.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
Elena Reshetova <elena.reshetova@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Hanjun Guo <guohanjun@huawei.com>,
Jan Glauber <jglauber@marvell.com>
Subject: Re: [PATCH v4 00/10] Rework REFCOUNT_FULL using atomic_fetch_* operations
Date: Wed, 30 Oct 2019 11:40:56 -0700 [thread overview]
Message-ID: <201910301139.ED3551BB14@keescook> (raw)
In-Reply-To: <20191030143035.19440-1-will@kernel.org>
On Wed, Oct 30, 2019 at 02:30:25PM +0000, Will Deacon wrote:
> Hi all,
>
> This is version four of the patches I previously posted here:
>
> v1: https://lkml.kernel.org/r/20190802101000.12958-1-will@kernel.org
> v2: https://lkml.kernel.org/r/20190827163204.29903-1-will@kernel.org
> v3: https://lkml.kernel.org/r/20191007154703.5574-1-will@kernel.org
>
> Changes since v3 include:
>
> - Add description of racy behaviour include/linux/refcount.h
> - Fix saturation behaviour in refcount_sub_and_test()
> - Added Acks and Tested-bys
Thanks again for this! I think this series is in good shape; I'm glad we
can sanely expand these protections.
--
Kees Cook
next prev parent reply other threads:[~2019-10-30 18:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 14:30 [PATCH v4 00/10] Rework REFCOUNT_FULL using atomic_fetch_* operations Will Deacon
2019-10-30 14:30 ` [PATCH v4 01/10] lib/refcount: Define constants for saturation and max refcount values Will Deacon
2019-10-30 14:30 ` [PATCH v4 02/10] lib/refcount: Ensure integer operands are treated as signed Will Deacon
2019-10-30 14:30 ` [PATCH v4 03/10] lib/refcount: Remove unused refcount_*_checked() variants Will Deacon
2019-10-30 14:30 ` [PATCH v4 04/10] lib/refcount: Move bulk of REFCOUNT_FULL implementation into header Will Deacon
2019-10-30 14:30 ` [PATCH v4 05/10] lib/refcount: Improve performance of generic REFCOUNT_FULL code Will Deacon
2019-10-30 14:30 ` [PATCH v4 06/10] lib/refcount: Move saturation warnings out of line Will Deacon
2019-10-30 18:39 ` Kees Cook
2019-10-30 14:30 ` [PATCH v4 07/10] lib/refcount: Consolidate REFCOUNT_{MAX,SATURATED} definitions Will Deacon
2019-10-30 14:30 ` [PATCH v4 08/10] refcount: Consolidate implementations of refcount_t Will Deacon
2019-10-30 14:30 ` [PATCH v4 09/10] lib/refcount: Remove unused 'refcount_error_report()' function Will Deacon
2019-10-30 14:30 ` [PATCH v4 10/10] drivers/lkdtm: Remove references to CONFIG_REFCOUNT_FULL Will Deacon
2019-10-30 18:40 ` Kees Cook [this message]
2019-11-07 13:00 ` [PATCH v4 00/10] Rework REFCOUNT_FULL using atomic_fetch_* operations Will Deacon
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=201910301139.ED3551BB14@keescook \
--to=keescook@chromium.org \
--cc=ard.biesheuvel@linaro.org \
--cc=elena.reshetova@intel.com \
--cc=guohanjun@huawei.com \
--cc=jglauber@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=will@kernel.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