From: Jan Kara <jack@suse.cz>
To: Elena Reshetova <elena.reshetova@intel.com>
Cc: jack@suse.cz, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, amir73il@gmail.com,
peterz@infradead.org, keescook@chromium.org
Subject: Re: [PATCH 1/2] fsnotify: convert fsnotify_group.refcnt from atomic_t to refcount_t
Date: Tue, 31 Oct 2017 11:58:43 +0100 [thread overview]
Message-ID: <20171031105843.GF8989@quack2.suse.cz> (raw)
In-Reply-To: <1508495162-32339-1-git-send-email-elena.reshetova@intel.com>
On Fri 20-10-17 13:26:01, 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 fsnotify_group.refcnt 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>
Thanks for the patch. I've added it to my tree.
Honza
> ---
> fs/notify/group.c | 6 +++---
> include/linux/fsnotify_backend.h | 3 ++-
> 2 files changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/fs/notify/group.c b/fs/notify/group.c
> index 3235753..b7a4b6a 100644
> --- a/fs/notify/group.c
> +++ b/fs/notify/group.c
> @@ -107,7 +107,7 @@ void fsnotify_destroy_group(struct fsnotify_group *group)
> */
> void fsnotify_get_group(struct fsnotify_group *group)
> {
> - atomic_inc(&group->refcnt);
> + refcount_inc(&group->refcnt);
> }
>
> /*
> @@ -115,7 +115,7 @@ void fsnotify_get_group(struct fsnotify_group *group)
> */
> void fsnotify_put_group(struct fsnotify_group *group)
> {
> - if (atomic_dec_and_test(&group->refcnt))
> + if (refcount_dec_and_test(&group->refcnt))
> fsnotify_final_destroy_group(group);
> }
>
> @@ -131,7 +131,7 @@ struct fsnotify_group *fsnotify_alloc_group(const struct fsnotify_ops *ops)
> return ERR_PTR(-ENOMEM);
>
> /* set to 0 when there a no external references to this group */
> - atomic_set(&group->refcnt, 1);
> + refcount_set(&group->refcnt, 1);
> atomic_set(&group->num_marks, 0);
> atomic_set(&group->user_waits, 0);
>
> diff --git a/include/linux/fsnotify_backend.h b/include/linux/fsnotify_backend.h
> index c6c6931..20a57ba 100644
> --- a/include/linux/fsnotify_backend.h
> +++ b/include/linux/fsnotify_backend.h
> @@ -17,6 +17,7 @@
> #include <linux/types.h>
> #include <linux/atomic.h>
> #include <linux/user_namespace.h>
> +#include <linux/refcount.h>
>
> /*
> * IN_* from inotfy.h lines up EXACTLY with FS_*, this is so we can easily
> @@ -135,7 +136,7 @@ struct fsnotify_group {
> * inotify_init() and the refcnt will hit 0 only when that fd has been
> * closed.
> */
> - atomic_t refcnt; /* things with interest in this group */
> + refcount_t refcnt; /* things with interest in this group */
>
> const struct fsnotify_ops *ops; /* how this group handles things */
>
> --
> 2.7.4
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2017-10-31 10:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 10:26 [PATCH 1/2] fsnotify: convert fsnotify_group.refcnt from atomic_t to refcount_t Elena Reshetova
2017-10-20 10:26 ` [PATCH 2/2] fsnotify: convert fsnotify_mark.refcnt " Elena Reshetova
2017-10-31 11:01 ` Jan Kara
2017-10-31 11:40 ` Reshetova, Elena
2017-10-31 10:58 ` Jan Kara [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-10-20 10:12 [PATCH 1/2] fsnotify: convert fsnotify_group.refcnt " Elena Reshetova
2017-10-20 10:28 ` 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=20171031105843.GF8989@quack2.suse.cz \
--to=jack@suse.cz \
--cc=amir73il@gmail.com \
--cc=elena.reshetova@intel.com \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).