public inbox for linux-bcache@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Lyle <mlyle@lyle.org>
To: Elena Reshetova <elena.reshetova@intel.com>, dm-devel@redhat.com
Cc: linux-bcache@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-raid@vger.kernel.org, kent.overstreet@gmail.com,
	koverstreet@google.com, ejt@redhat.comg, snitzer@redhat.com,
	shli@kernel.org, agk@redhat.com, peterz@infradead.org,
	keescook@chromium.org
Subject: Re: [PATCH 1/4] bcache: convert cached_dev.count from atomic_t to refcount_t
Date: Fri, 20 Oct 2017 11:39:42 -0700	[thread overview]
Message-ID: <8bd05fae-d41f-24e7-4e58-bf07d9a09a99@lyle.org> (raw)
In-Reply-To: <1508485059-21881-2-git-send-email-elena.reshetova@intel.com>

On 10/20/2017 12:37 AM, Elena Reshetova wrote:
> atomic_t variables are currently used to implement reference
> counters with the following properties:
>  - counter is initialized to 1 using atomic_set()
>  - a resource is freed upon counter reaching zero
>  - once counter reaches zero, its further
>    increments aren't allowed
>  - counter schema uses basic atomic operations
>    (set, inc, inc_not_zero, dec_and_test, etc.)
> 
> Such atomic variables should be converted to a newly provided
> refcount_t type and API that prevents accidental counter overflows
> and underflows. This is important since overflows and underflows
> can lead to use-after-free situation and be exploitable.
> 
> The variable cached_dev.count is used as pure reference counter.
> Convert it to refcount_t and fix up the operations.
> 
> Suggested-by: Kees Cook <keescook@chromium.org>
> Reviewed-by: David Windsor <dwindsor@gmail.com>
> Reviewed-by: Hans Liljestrand <ishkamiel@gmail.com>
> Signed-off-by: Elena Reshetova <elena.reshetova@intel.com>

Reviewed-by: Michael Lyle <mlyle@lyle.org>

Thanks for this-- I'm including it in my tree for possible inclusion in
4.15 (I've already sent my main chunk of changes upwards).

Mike

  reply	other threads:[~2017-10-20 18:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-20  7:37 [PATCH 0/4] dm and bcache refcount conversions Elena Reshetova
2017-10-20  7:37 ` [PATCH 1/4] bcache: convert cached_dev.count from atomic_t to refcount_t Elena Reshetova
2017-10-20 18:39   ` Michael Lyle [this message]
2017-10-23  6:45     ` Reshetova, Elena
2017-10-20  7:37 ` [PATCH 2/4] dm cache: convert dm_cache_metadata.ref_count " Elena Reshetova
2017-10-20  7:37 ` [PATCH 3/4] dm: convert dm_dev_internal.count " Elena Reshetova
2017-11-23 15:49   ` [dm-devel] " Alasdair G Kergon
2017-11-24  7:36     ` Reshetova, Elena
2017-11-25  5:56       ` Mike Snitzer
2017-11-28 10:07         ` Reshetova, Elena
2017-11-28 19:02           ` Mike Snitzer
2017-11-29  8:05             ` Reshetova, Elena
2017-10-20  7:37 ` [PATCH 4/4] dm: convert table_device.count " Elena Reshetova
2017-11-23 15:19   ` Zdenek Kabelac
2017-11-24  8:29     ` Reshetova, Elena
2017-11-24 14:04       ` Alasdair G Kergon
2017-11-24 14:44         ` Reshetova, Elena

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=8bd05fae-d41f-24e7-4e58-bf07d9a09a99@lyle.org \
    --to=mlyle@lyle.org \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=ejt@redhat.comg \
    --cc=elena.reshetova@intel.com \
    --cc=keescook@chromium.org \
    --cc=kent.overstreet@gmail.com \
    --cc=koverstreet@google.com \
    --cc=linux-bcache@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=shli@kernel.org \
    --cc=snitzer@redhat.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