From: Boqun Feng <boqun.feng@gmail.com>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: rcu@vger.kernel.org, Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Waiman Long <longman@redhat.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Josh Triplett <josh@joshtriplett.org>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Frederic Weisbecker <frederic@kernel.org>,
Neeraj Upadhyay <quic_neeraju@quicinc.com>,
Joel Fernandes <joel@joelfernandes.org>,
Shuah Khan <shuah@kernel.org>,
David Woodhouse <dwmw2@infradead.org>,
Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, seanjc@google.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH rcu 1/7] locking/lockdep: Introduce lock_sync()
Date: Mon, 20 Mar 2023 10:50:32 -0700 [thread overview]
Message-ID: <ZBic6FfmVmMERQXm@boqun-archlinux> (raw)
In-Reply-To: <20230320170614.ttnqyhemnelgmzgd@offworld>
On Mon, Mar 20, 2023 at 10:06:14AM -0700, Davidlohr Bueso wrote:
> On Thu, 16 Mar 2023, Boqun Feng wrote:
>
> > +/*
> > + * lock_sync() - A special annotation for synchronize_{s,}rcu()-like API.
> > + *
> > + * No actual critical section is created by the APIs annotated with this: these
> > + * APIs are used to wait for one or multiple critical sections (on other CPUs
> > + * or threads), and it means that calling these APIs inside these critical
> > + * sections is potential deadlock.
> > + *
> > + * This annotation acts as an acqurie+release anontation pair with hardirqoff
> ^acquire
Good eye! Applied locally.
Regards,
Boqun
next prev parent reply other threads:[~2023-03-20 17:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 3:13 [PATCH rcu 0/7] RCU-related lockdep changes for v6.4 Boqun Feng
2023-03-17 3:13 ` [PATCH rcu 1/7] locking/lockdep: Introduce lock_sync() Boqun Feng
2023-03-20 17:06 ` Davidlohr Bueso
2023-03-20 17:50 ` Boqun Feng [this message]
2023-03-17 3:13 ` [PATCH rcu 2/7] rcu: Annotate SRCU's update-side lockdep dependencies Boqun Feng
2023-03-17 3:13 ` [PATCH rcu 3/7] locking: Reduce the number of locks in ww_mutex stress tests Boqun Feng
2023-03-17 18:38 ` Paul E. McKenney
2023-03-17 21:26 ` Boqun Feng
2023-03-17 3:13 ` [PATCH rcu 4/7] locking/lockdep: Improve the deadlock scenario print for sync and read lock Boqun Feng
2023-03-20 12:13 ` Peter Zijlstra
2023-03-20 17:50 ` Boqun Feng
2023-03-17 3:13 ` [PATCH rcu 5/7] rcutorture: Add SRCU deadlock scenarios Boqun Feng
2023-03-17 3:13 ` [PATCH rcu 6/7] rcutorture: Add RCU Tasks Trace and " Boqun Feng
2023-03-17 3:13 ` [PATCH rcu 7/7] rcutorture: Add srcu_lockdep.sh Boqun Feng
2023-03-20 18:19 ` Boqun Feng
2023-03-20 19:09 ` Paul E. McKenney
2023-03-20 19:28 ` Boqun Feng
2023-03-20 20:22 ` Paul E. McKenney
2023-03-20 20:26 ` Boqun Feng
2023-03-20 20:36 ` Paul E. McKenney
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=ZBic6FfmVmMERQXm@boqun-archlinux \
--to=boqun.feng@gmail.com \
--cc=dave@stgolabs.net \
--cc=dwmw2@infradead.org \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=quic_neeraju@quicinc.com \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=seanjc@google.com \
--cc=shuah@kernel.org \
--cc=will@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.