From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753085Ab3JWSXK (ORCPT ); Wed, 23 Oct 2013 14:23:10 -0400 Received: from mail-pa0-f52.google.com ([209.85.220.52]:59706 "EHLO mail-pa0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752129Ab3JWSXI (ORCPT ); Wed, 23 Oct 2013 14:23:08 -0400 Message-ID: <52681407.8060804@linaro.org> Date: Wed, 23 Oct 2013 11:23:03 -0700 From: John Stultz User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: John Stultz , LKML CC: Eric Dumazet , Thomas Petazzoni , Mirko Lindner , Stephen Hemminger , Roger Luethi , Patrick McHardy , Rusty Russell , "Michael S. Tsirkin" , Alexey Kuznetsov , James Morris , Hideaki YOSHIFUJI , Wensong Zhang , Simon Horman , Julian Anastasov , Jesse Gross , Mathieu Desnoyers , Steven Rostedt , Peter Zijlstra , Ingo Molnar , Thomas Gleixner , "David S. Miller" , netdev@vger.kernel.org, netfilter-devel@vger.kernel.org Subject: Re: [PATCH 1/4] [RFC] net: Explicitly initialize u64_stats_sync structures for lockdep References: <1381186321-4906-1-git-send-email-john.stultz@linaro.org> <1381186321-4906-2-git-send-email-john.stultz@linaro.org> In-Reply-To: <1381186321-4906-2-git-send-email-john.stultz@linaro.org> X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/07/2013 03:51 PM, John Stultz wrote: > In order to enable lockdep on seqcount/seqlock structures, we > must explicitly initialize any locks. > > The u64_stats_sync structure, uses a seqcount, and thus we need > to introduce a u64_stats_init() function and use it to initialize > the structure. > > This unfortunately adds a lot of fairly trivial initialization code > to a number of drivers. But the benefit of ensuring correctness makes > this worth while. > > Because these changes are required for lockdep to be enabled, and the > changes are quite trivial, I've not yet split this patch out into 30-some > separate patches, as I figured it would be better to get the various > maintainers thoughts on how to best merge this change along with > the seqcount lockdep enablement. Just wanted to ping folks on this patch, as I haven't gotten any feedback. As its a prereq for the seqcount lockdep support, I'd like to get it queued/merged, but I'm not sure what the right maintainer path or approach should be. 1) Do folks prefer to see this patch split up into 30-some separate trivial clenaup patches, or have it go in all as one logical change? 2) Would folks want this patch (in whichever form) to be merged separately via the networking maintainers, or can it be merged via -tip as part of the seqcount lockdep series? thanks -john