[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Sat, 12 Dec 2015 10:55:59 +0800
From: Boqun Feng <boqun.feng@...il.com>
To: linux-sparse@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: Christopher Li <sparse@...isli.org>,
"Paul E . McKenney" <paulmck@...ux.vnet.ibm.com>,
Josh Triplett <josh@...htriplett.org>,
Steven Rostedt <rostedt@...dmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Lai Jiangshan <jiangshanlai@...il.com>,
Andy Whitcroft <apw@...onical.com>,
Joe Perches <joe@...ches.com>,
Thomas Gleixner <tglx@...utronix.de>,
Jiang Liu <jiang.liu@...ux.intel.com>,
Marc Zyngier <marc.zyngier@....com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Russell King <rmk+kernel@....linux.org.uk>,
Brian Norris <computersforpeace@...il.com>,
Peter Zijlstra <peterz@...radead.org>,
Boqun Feng <boqun.feng@...il.com>
Subject: [RFC 0/3] sparse: Introduce __private to privatize members of structs
Hi all,
As I proposed:
http://marc.info/?l=linux-arm-kernel&m=144944469805753
, we can define a __private modifier for sparse to detect misuses of private
members of structs. This could make maintenace a little easier and prevent some
potential bugs.
This patchset serves as a POC and consists of three patches:
1. Introduce __private and related macro, also improve compiler.h a litte
bit
2. Privatize rcu_node::lock
3. Privatize irq_common_data::state_use_accessors
This patchset is against
-rcu/rcu/next 5f343fc7f0ce7edfe344e7cc5afdfe145a18f802
because this depends on commits:
"rcu: Create transitive rnp->lock acquisition functions"
and
"rcu: Add transitivity to remaining rcu_node ->lock acquisitions
I tried to use 0day to test this, but seems the email transfer from 0day to my
mail box is very slow recently, so I haven't received a recent result yet. But
as one can see, this patchset doesn't have any functional modification, the 0day
may not find anything interesting ;-)
Looking forward to any suggestion, question and comment ;-)
Regards,
Boqun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists