public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: "Reshetova, Elena" <elena.reshetova@intel.com>
Cc: Xiaoming Ni <nixiaoming@huawei.com>,
	Peter Zijlstra <peterz@infradead.org>,
	David Windsor <dwindsor@gmail.com>,
	Hans Liljestrand <ishkamiel@gmail.com>,
	Paul Moore <paul@paul-moore.com>,
	"edumazet@google.com" <edumazet@google.com>,
	"paulmck@kernel.org" <paulmck@kernel.org>,
	David Howells <dhowells@redhat.com>,
	"shakeelb@google.com" <shakeelb@google.com>,
	James Morris <jamorris@linux.microsoft.com>,
	"alex.huangjianhui@huawei.com" <alex.huangjianhui@huawei.com>,
	"dylix.dailei@huawei.com" <dylix.dailei@huawei.com>,
	"chenzefeng2@huawei.com" <chenzefeng2@huawei.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] Convert nsproxy, groups, and creds to refcount_t
Date: Mon, 15 Jun 2020 11:08:33 -0700	[thread overview]
Message-ID: <202006151108.5B25D5A31@keescook> (raw)
In-Reply-To: <CY4PR1101MB23261B27ACF9D7FBC3969318E79C0@CY4PR1101MB2326.namprd11.prod.outlook.com>

On Mon, Jun 15, 2020 at 05:35:58AM +0000, Reshetova, Elena wrote:
> > On Mon, Jun 15, 2020 at 10:10:08AM +0800, Xiaoming Ni wrote:
> > > On 2020/6/13 2:34, Kees Cook wrote:
> > > > This series was never applied[1], and was recently pointed out as
> > > > missing[2]. If someone has a tree for this, please take it. Otherwise,
> > > > please Ack and I'll send it to Linus.
> > > >
> > > > Thanks!
> > > >
> > > > -Kees
> > > >
> > > > [1] https://lore.kernel.org/lkml/20190306110549.7628-1-
> > elena.reshetova@intel.com/
> > > > [2] https://lore.kernel.org/lkml/1591957695-118312-1-git-send-email-
> > nixiaoming@huawei.com/
> > > >
> > > > Elena Reshetova (3):
> > > >    nsproxy: convert nsproxy.count to refcount_t
> > > >    groups: convert group_info.usage to refcount_t
> > > >    creds: convert cred.usage to refcount_t
> > > >
> > > >   include/linux/cred.h    | 15 +++++++-------
> > > >   include/linux/nsproxy.h |  7 +++----
> > > >   kernel/cred.c           | 44 ++++++++++++++++++++---------------------
> > > >   kernel/groups.c         |  2 +-
> > > >   kernel/nsproxy.c        |  6 +++---
> > > >   net/sunrpc/auth.c       |  2 +-
> > > >   6 files changed, 38 insertions(+), 38 deletions(-)
> > > >
> > >
> > > Should mm->mm_users also be replaced by refcount_t?
> > 
> > I'll say "yes". :)
> > https://lore.kernel.org/lkml/1487671124-11188-1-git-send-email-
> > elena.reshetova@intel.com/
> > 
> > > In addition, is it better to change all variables that use
> > > atomic_dec_and_test to control the release process to refconut_t?
> > 
> > For the most part, yes. The following may find a lot of them:
> > scripts/coccinelle/api/atomic_as_refcounter.cocci
> > 
> > If you can go through that and double check for prior series from Elena,
> > we can get through all the rest of them.
> 
> I have these ones also here in case anyone is interested:
> https://github.com/ereshetova/linux-stable/commits/refcount_t_fs
> https://github.com/ereshetova/linux-stable/commits/refcount_t_block
> 
> They haven't been rebased for a while, but if there is an interest, 
> I can certainly do it.

That would be great; yes!

-- 
Kees Cook

  reply	other threads:[~2020-06-15 18:08 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-12 18:34 [PATCH 0/3] Convert nsproxy, groups, and creds to refcount_t Kees Cook
2020-06-12 18:34 ` [PATCH 1/3] nsproxy: convert nsproxy.count " Kees Cook
2020-06-12 18:34 ` [PATCH 2/3] groups: convert group_info.usage " Kees Cook
2020-06-15  0:57   ` [groups] 67467ae141: will-it-scale.per_process_ops 4.3% improvement kernel test robot
2020-06-12 18:34 ` [PATCH 3/3] creds: convert cred.usage to refcount_t Kees Cook
2020-06-15  2:02   ` Xiaoming Ni
2020-06-15  2:10 ` [PATCH 0/3] Convert nsproxy, groups, and creds " Xiaoming Ni
2020-06-15  3:55   ` Kees Cook
2020-06-15  5:35     ` Reshetova, Elena
2020-06-15 18:08       ` Kees Cook [this message]
2020-06-18  7:39         ` Reshetova, Elena
2020-07-21 11:02           ` David Howells
2020-07-21 10:51     ` David Howells
2020-07-21 18:44       ` Kees Cook
2020-07-21 19:51         ` Peter Zijlstra
2020-07-28 10:56           ` David Howells
2020-07-29 11:11             ` [RFC][PATCH] locking/refcount: Provide __refcount API to obtain the old value peterz
2020-07-29 11:37               ` peterz
2020-07-29 19:29                 ` Kees Cook
2020-07-29 19:30               ` Kees Cook
2020-07-29 20:41               ` David Howells
2020-07-29 20:52                 ` Kees Cook
2020-08-27  7:54               ` [tip: locking/core] " tip-bot2 for Peter Zijlstra
2020-09-21 11:22               ` [RFC][PATCH] " Will Deacon
2021-01-26 11:25                 ` David Howells
2020-07-28 11:01         ` [PATCH 0/3] Convert nsproxy, groups, and creds to refcount_t David Howells

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=202006151108.5B25D5A31@keescook \
    --to=keescook@chromium.org \
    --cc=alex.huangjianhui@huawei.com \
    --cc=chenzefeng2@huawei.com \
    --cc=dhowells@redhat.com \
    --cc=dwindsor@gmail.com \
    --cc=dylix.dailei@huawei.com \
    --cc=edumazet@google.com \
    --cc=elena.reshetova@intel.com \
    --cc=ishkamiel@gmail.com \
    --cc=jamorris@linux.microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nixiaoming@huawei.com \
    --cc=paul@paul-moore.com \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=shakeelb@google.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