From: Waiman Long <longman@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Davidlohr Bueso <dave@stgolabs.net>,
"Theodore Y. Ts'o" <tytso@mit.edu>,
Oleg Nesterov <oleg@redhat.com>,
Amir Goldstein <amir73il@gmail.com>, Jan Kara <jack@suse.cz>,
Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH v3 2/2] locking/percpu-rwsem: Annotate rwsem ownership transfer by setting RWSEM_OWNER_UNKNOWN
Date: Tue, 15 May 2018 14:02:00 -0400 [thread overview]
Message-ID: <1baa1a1a-a4a7-d706-8c01-5ff6a8757f97@redhat.com> (raw)
In-Reply-To: <20180515175805.GN12217@hirez.programming.kicks-ass.net>
On 05/15/2018 01:58 PM, Peter Zijlstra wrote:
> On Tue, May 15, 2018 at 01:38:04PM -0400, Waiman Long wrote:
>> +/*
>> + * Owner value to indicate the rwsem's owner is not currently known.
>> + */
>> +#define RWSEM_OWNER_UNKNOWN ((struct task_struct *)-1)
> It might be nice to comment that this works and relies on having that
> ANON_OWNER bit set.
I am just trying not to expose internal working of rwsem, but I can
document that one of the bits is the real deal without specifying which one.
Cheers,
Longman
next prev parent reply other threads:[~2018-05-15 18:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 17:38 [PATCH v3 0/2] locking/rwsem: Fix DEBUG_RWSEM warning from thaw_super() Waiman Long
2018-05-15 17:38 ` [PATCH v3 1/2] locking/rwsem: Add a new RWSEM_ANONYMOUSLY_OWNED flag Waiman Long
2018-05-15 17:46 ` Peter Zijlstra
2018-05-15 17:48 ` Waiman Long
2018-05-15 17:48 ` Peter Zijlstra
2018-05-15 17:52 ` Waiman Long
2018-05-15 17:55 ` Peter Zijlstra
2018-05-15 17:56 ` Waiman Long
2018-05-15 18:02 ` Peter Zijlstra
2018-05-15 17:38 ` [PATCH v3 2/2] locking/percpu-rwsem: Annotate rwsem ownership transfer by setting RWSEM_OWNER_UNKNOWN Waiman Long
2018-05-15 17:58 ` Peter Zijlstra
2018-05-15 18:02 ` Waiman Long [this message]
2018-05-15 18:05 ` Amir Goldstein
2018-05-15 18:45 ` Waiman Long
2018-05-15 18:05 ` Peter Zijlstra
2018-05-15 18:35 ` Waiman Long
2018-05-15 18:02 ` Matthew Wilcox
2018-05-15 18:07 ` Peter Zijlstra
2018-05-15 18:45 ` Waiman Long
2018-05-15 21:21 ` Matthew Wilcox
2018-05-15 21:30 ` Waiman Long
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=1baa1a1a-a4a7-d706-8c01-5ff6a8757f97@redhat.com \
--to=longman@redhat.com \
--cc=amir73il@gmail.com \
--cc=dave@stgolabs.net \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tytso@mit.edu \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).