From: David Howells <dhowells@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: dhowells@redhat.com, Kees Cook <keescook@chromium.org>,
Xiaoming Ni <nixiaoming@huawei.com>,
David Windsor <dwindsor@gmail.com>,
Hans Liljestrand <ishkamiel@gmail.com>,
Elena Reshetova <elena.reshetova@intel.com>,
Paul Moore <paul@paul-moore.com>,
edumazet@google.com, paulmck@kernel.org, shakeelb@google.com,
James Morris <jamorris@linux.microsoft.com>,
alex.huangjianhui@huawei.com, dylix.dailei@huawei.com,
chenzefeng2@huawei.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] Convert nsproxy, groups, and creds to refcount_t
Date: Tue, 28 Jul 2020 11:56:38 +0100 [thread overview]
Message-ID: <3211866.1595933798@warthog.procyon.org.uk> (raw)
In-Reply-To: <20200721195132.GJ10769@hirez.programming.kicks-ass.net>
Peter Zijlstra <peterz@infradead.org> wrote:
> > Please do not _undo_ the changes; just add the API you need.
>
> add_return and sub_return are horrible interface for refcount, which is
> the problem.
>
> If you meant: refcount_dec(), but want the old value for tracing, you
> want a different ordering than if you wanted to do
> refcount_dec_and_test(); dec_return can't know this.
>
> David, would something like a __refcount_*() API work where there is a
> 3rd argument (int *), which, if !NULL, will be assigned the old value?
That would be fine, though the number needs to be something I can interpret
easily when looking through the traces. It would also be okay if there was an
interpretation function that I could use in the trace point when setting the
variable.
Say:
void rxrpc_get_call(struct rxrpc_call *call, enum rxrpc_call_trace op)
{
const void *here = __builtin_return_address(0);
unsigned int n;
refcount_inc_return(&call->usage, &n);
trace_rxrpc_call(call->debug_id, op, n, here, NULL);
}
then:
TRACE_EVENT(rxrpc_call,
TP_PROTO(..., int usage, ...),
TP_ARGS(...),
TP_STRUCT__entry(
...
__field(int, usage)
...
),
TP_fast_assign(
...
__entry->usage = refcount_interpret(usage);
...
),
TP_printk("... u=%d ...",
...
__entry->usage,
...)
);
so that it looks like the refcount is 'complete' at 0.
David
next prev parent reply other threads:[~2020-07-28 10:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 18:34 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
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 [this message]
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-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-29 20:41 ` David Howells
2020-07-29 20:52 ` Kees Cook
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=3211866.1595933798@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=alex.huangjianhui@huawei.com \
--cc=chenzefeng2@huawei.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=keescook@chromium.org \
--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
Powered by JetHome