On Sat, Nov 16, 2013 at 12:32:16PM +0800, Ding Tianhong wrote:
> 于 2013/11/16 8:40, Paul E. McKenney 写道:
> > From: "Paul E. McKenney"
> >
> > The sparse checking for rcu_assign_pointer() was recently upgraded
> > to reject non-__kernel address spaces. This also rejects __rcu,
> > which is almost
On Sat, Nov 16, 2013 at 12:32:16PM +0800, Ding Tianhong wrote:
于 2013/11/16 8:40, Paul E. McKenney 写道:
From: Paul E. McKenney paul...@linux.vnet.ibm.com
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
于 2013/11/16 8:40, Paul E. McKenney 写道:
> From: "Paul E. McKenney"
>
> The sparse checking for rcu_assign_pointer() was recently upgraded
> to reject non-__kernel address spaces. This also rejects __rcu,
> which is almost always the right thing to do. However, the uses in
>
From: "Paul E. McKenney"
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the uses in
bond_change_active_slave() and __bond_release_one() are legitimate:
From: Paul E. McKenney paul...@linux.vnet.ibm.com
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the uses in
bond_change_active_slave() and
于 2013/11/16 8:40, Paul E. McKenney 写道:
From: Paul E. McKenney paul...@linux.vnet.ibm.com
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the uses in
6 matches
Mail list logo