From: Andrea Parri <andrea.parri@amarulasolutions.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Elena Reshetova <elena.reshetova@intel.com>,
Kees Cook <keescook@chromium.org>,
Peter Zijlstra <peterz@infradead.org>,
Alan Stern <stern@rowland.harvard.edu>,
"Paul E. McKenney" <paulmck@linux.ibm.com>,
Will Deacon <will.deacon@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Anders Roxell <anders.roxell@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kcov: convert kcov.refcount to refcount_t
Date: Mon, 21 Jan 2019 15:44:46 +0100 [thread overview]
Message-ID: <20190121144446.GA8926@andrea> (raw)
In-Reply-To: <CACT4Y+aF8+RqEk8RJn3G4nN8bCAxuci5W9YXa=cFq4c-QC3kgg@mail.gmail.com>
On Mon, Jan 21, 2019 at 01:29:11PM +0100, Dmitry Vyukov wrote:
> On Mon, Jan 21, 2019 at 12:45 PM Andrea Parri
> <andrea.parri@amarulasolutions.com> wrote:
> >
> > On Mon, Jan 21, 2019 at 10:52:37AM +0100, Dmitry Vyukov wrote:
> >
> > [...]
> >
> > > > Am I missing something or refcount_dec_and_test does not in fact
> > > > provide ACQUIRE ordering?
> > > >
> > > > +case 5) - decrement-based RMW ops that return a value
> > > > +-----------------------------------------------------
> > > > +
> > > > +Function changes:
> > > > + atomic_dec_and_test() --> refcount_dec_and_test()
> > > > + atomic_sub_and_test() --> refcount_sub_and_test()
> > > > + no atomic counterpart --> refcount_dec_if_one()
> > > > + atomic_add_unless(&var, -1, 1) --> refcount_dec_not_one(&var)
> > > > +
> > > > +Memory ordering guarantees changes:
> > > > + fully ordered --> RELEASE ordering + control dependency
> > > >
> > > > I think that's against the expected refcount guarantees. When I
> > > > privatize an atomic_dec_and_test I would expect that not only stores,
> > > > but also loads act on a quiescent object. But loads can hoist outside
> > > > of the control dependency.
> > > >
> > > > Consider the following example, is it the case that the BUG_ON can still fire?
> >
> > Can't it fire in an SC world? (wrong example, or a Monday morning? ;D)
>
> I don't see how. Maybe there is a stupid off-by-one, but overall
> that's the example I wanted to show. refcount is 2, each thread sets
> own done flag, drops refcount, last thread checks done flag of the
> other thread.
You're right: looking at the example again, I think that the BUG_ON()
in your example can indeed trigger with a CTRL+RELEASE semantics (but
_not with the fully-ordered semantics).
I apologize for the confusion (it must have been _my Monday... ;-/).
Andrea
>
>
>
> > > > struct X {
> > > > refcount_t rc; // == 2
> > > > int done1, done2; // == 0
> > > > };
> > > >
> > > > // thread 1:
> > > > x->done1 = 1;
> > > > if (refcount_dec_and_test(&x->rc))
> > > > BUG_ON(!x->done2);
> > > >
> > > > // thread 2:
> > > > x->done2 = 1;
> > > > if (refcount_dec_and_test(&x->rc))
> > > > BUG_ON(!x->done1);
next prev parent reply other threads:[~2019-01-21 14:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 10:27 [PATCH] kcov: convert kcov.refcount to refcount_t Elena Reshetova
2019-01-16 12:51 ` Dmitry Vyukov
2019-01-21 9:52 ` Dmitry Vyukov
2019-01-21 11:45 ` Andrea Parri
2019-01-21 12:29 ` Dmitry Vyukov
2019-01-21 14:44 ` Andrea Parri [this message]
2019-01-21 13:18 ` Peter Zijlstra
2019-01-21 16:05 ` Alan Stern
2019-01-21 17:00 ` Dmitry Vyukov
2019-01-22 9:04 ` Peter Zijlstra
2019-01-22 23:22 ` Kees Cook
2019-01-25 9:02 ` Reshetova, Elena
2019-01-25 10:31 ` Peter Zijlstra
2019-01-27 18:41 ` Reshetova, Elena
2019-01-28 8:33 ` Dmitry Vyukov
2019-01-28 9:28 ` Peter Zijlstra
2019-01-21 11:51 ` Andrea Parri
2019-01-21 12:38 ` Mark Rutland
2019-01-21 12:42 ` Dmitry Vyukov
2019-01-21 14:07 ` Reshetova, Elena
2019-01-21 17:07 ` Dmitry Vyukov
2019-01-31 10:03 ` Reshetova, Elena
2019-01-31 10:06 ` Dmitry Vyukov
2019-01-31 10:09 ` Reshetova, Elena
2019-01-31 10:33 ` Dmitry Vyukov
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=20190121144446.GA8926@andrea \
--to=andrea.parri@amarulasolutions.com \
--cc=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=aryabinin@virtuozzo.com \
--cc=dvyukov@google.com \
--cc=elena.reshetova@intel.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=paulmck@linux.ibm.com \
--cc=peterz@infradead.org \
--cc=stern@rowland.harvard.edu \
--cc=will.deacon@arm.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