From: Peter Zijlstra <peterz@infradead.org>
To: John Stultz <john.stultz@linaro.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Eric Dumazet <eric.dumazet@gmail.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"David S. Miller" <davem@davemloft.net>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
James Morris <jmorris@namei.org>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>
Subject: Re: [PATCH 0/4] Lockdep enablement for seqcount/seqlocks (v2)
Date: Tue, 29 Oct 2013 15:09:26 +0100 [thread overview]
Message-ID: <20131029140926.GE16117@laptop.programming.kicks-ass.net> (raw)
In-Reply-To: <1381186321-4906-1-git-send-email-john.stultz@linaro.org>
On Mon, Oct 07, 2013 at 03:51:57PM -0700, John Stultz wrote:
> Just wanted to send this out again for further feedback.
>
> This patch series enables lockdep for seqcount/seqlock structures,
> as well as provides the required cleanups to explicitly initialize
> the seqcount structures on u64_stat_sync users.
>
> In addition the last two patches in this provide fixes to
> some of the issues the new lockdep infrastructure caught.
>
> I'd greatly appreciate any thoughts or feedback on the series!
> Particularly on how the u64_stats_sync initialization changes
> should be merged.
I've picked up all 4 patches for the lockdep tree; I've tried against
-next of today (20131029) and found no collisions with networking so I'm
hoping all will land well.
Please anybody holler if they disagree/want things done differently.
prev parent reply other threads:[~2013-10-29 14:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 22:51 [PATCH 0/4] Lockdep enablement for seqcount/seqlocks (v2) John Stultz
2013-10-07 22:51 ` [PATCH 1/4] [RFC] net: Explicitly initialize u64_stats_sync structures for lockdep John Stultz
2013-10-07 22:51 ` John Stultz
2013-10-23 18:23 ` John Stultz
2013-10-23 19:37 ` Julian Anastasov
2013-10-23 19:37 ` Julian Anastasov
2013-11-06 13:20 ` [tip:core/locking] " tip-bot for John Stultz
2013-10-07 22:51 ` [PATCH 2/4] [RFC] seqcount: Add lockdep functionality to seqcount/seqlock structures John Stultz
2013-11-06 13:20 ` [tip:core/locking] " tip-bot for John Stultz
2013-10-07 22:52 ` [PATCH 3/4] [RFC] cpuset: Fix potential deadlock w/ set_mems_allowed John Stultz
2013-11-06 13:20 ` [tip:core/locking] " tip-bot for John Stultz
2013-10-07 22:52 ` [PATCH 4/4] [RFC] ipv6: Fix for possible ipv6 seqlock deadlock John Stultz
2013-10-07 23:54 ` Eric Dumazet
2013-11-06 13:20 ` [tip:core/locking] ipv6: Fix " tip-bot for John Stultz
2013-10-29 14:09 ` Peter Zijlstra [this message]
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=20131029140926.GE16117@laptop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jmorris@namei.org \
--cc=john.stultz@linaro.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=yoshfuji@linux-ipv6.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.