Re: [PATCH 2/2] ipvs: Use cond_resched_rcu_lock() helper when dumping connections

[Peter Zijlstra <peterz@xxxxxxxxxxxxx>]

On Fri, Apr 26, 2013 at 10:45:08AM +0900, Simon Horman wrote:

> @@ -975,8 +975,7 @@ static void *ip_vs_conn_array(struct seq_file *seq, 
> loff_t pos)
>                               return cp;
>                       }
>               }
> -             rcu_read_unlock();
> -             rcu_read_lock();
> +             cond_resched_rcu_lock();
>       }


While I agree with the sentiment I do find it a somewhat dangerous construct in
that it might become far too easy to keep an RCU reference over this break and
thus violate the RCU premise.

Is there anything that can detect this? Sparse / cocinelle / smatch? If so it
would be great to add this to these checkers.
--
To unsubscribe from this list: send the line "unsubscribe lvs-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html