From: Peter Zijlstra <peterz@infradead.org>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: John Stultz <john.stultz@linaro.org>,
Jeff Layton <jeff.layton@primarydata.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Linux Kernel mailing list <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: nfs4_do_reclaim lockdep pop in v3.15.0-rc1
Date: Tue, 3 Jun 2014 12:48:23 +0200 [thread overview]
Message-ID: <20140603104823.GU11096@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <CAHQdGtQhurcOsAii7PYNZwEL4Xm-8a2CKBkS4OhrS0FhaAX3Aw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 381 bytes --]
On Mon, Jun 02, 2014 at 08:59:21PM -0400, Trond Myklebust wrote:
>
> I can change the write seqcount to use raw_write_seqcount(), but that
> doesn't answer the question of why raw_seqcount_begin() is the _only_
> object out there with a "raw_" prefix, that doesn't explicitly disable
> lockdep checking.
raw_spinlock_t has lockdep too.. just to add to the confusion.
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-06-03 10:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 14:49 nfs4_do_reclaim lockdep pop in v3.15.0-rc1 Jeff Layton
2014-06-02 15:16 ` Trond Myklebust
2014-06-02 16:02 ` Trond Myklebust
2014-06-02 22:12 ` John Stultz
2014-06-02 22:42 ` Trond Myklebust
2014-06-02 22:49 ` John Stultz
2014-06-03 0:59 ` Trond Myklebust
2014-06-03 3:19 ` John Stultz
2014-06-03 10:55 ` Peter Zijlstra
2014-06-03 14:25 ` Trond Myklebust
2014-06-03 10:48 ` Peter Zijlstra [this message]
2014-06-19 12:36 ` [tip:locking/core] lockdep: Revert lockdep check in raw_seqcount_begin() tip-bot for Trond Myklebust
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=20140603104823.GU11096@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=jeff.layton@primarydata.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.org \
--cc=trond.myklebust@primarydata.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 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.