From: Peter Zijlstra <peterz@infradead.org>
To: Jules Irenge <jbi.octave@gmail.com>
Cc: bokun.feng@gmail.com, mingo@redhat.com, acme@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@redhat.com, namhyung@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kernel: events: add releases() notation
Date: Mon, 16 Dec 2019 09:31:28 +0100 [thread overview]
Message-ID: <20191216083128.GI2844@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20191216002400.89985-1-jbi.octave@gmail.com>
On Mon, Dec 16, 2019 at 12:24:00AM +0000, Jules Irenge wrote:
> Add releases() notation to remove issue detected by sparse
> context imbalance in perf_output_end() - unexpected unlock
None of the perf code uses the __acquire / __release annotations crud.
Also, your annotation is broken, I think it should be __releases(RCU) or
something like that.
next prev parent reply other threads:[~2019-12-16 8:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 0:24 Jules Irenge
2019-12-16 8:31 ` Peter Zijlstra [this message]
2019-12-16 13:37 ` Jules Irenge
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=20191216083128.GI2844@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=bokun.feng@gmail.com \
--cc=jbi.octave@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®