On Fri, Jan 27, 2017 at 09:07:38AM +0100, Simon Horman wrote: > On Thu, Jan 26, 2017 at 10:49:10PM +0200, Julian Anastasov wrote: > > > > Hello, > > > > On Mon, 23 Jan 2017, David Windsor wrote: > > > > > Currently, the ip_vs_dest cache frees ip_vs_dest objects when their > > > reference count becomes < 0. Aside from not being semantically sound, > > > this is problematic for the new type refcount_t, which will be introduced > > > shortly in a separate patch. refcount_t is the new kernel type for > > > holding reference counts, and provides overflow protection and a > > > constrained interface relative to atomic_t (the type currently being > > > used for kernel reference counts). > > > > > > Per Julian Anastasov: "The problem is that dest_trash currently holds > > > deleted dests (unlinked from RCU lists) with refcnt=0." Changing > > > dest_trash to hold dest with refcnt=1 will allow us to free ip_vs_dest > > > structs when their refcnt=0, in ip_vs_dest_put_and_free(). > > > > > > Signed-off-by: David Windsor <dwindsor@xxxxxxxxx> > > > > Thanks! I tested the first version and this one > > just adds the needed changes in comments, so > > > > Signed-off-by: Julian Anastasov <ja@xxxxxx> > > > > Simon and Pablo, this is more appropriate for > > ipvs-next/nf-next. Please apply! > > Pablo, would you mind taking this one directly into nf-next? > > Signed-off-by: Simon Horman <horms@xxxxxxxxxxxx> Sure, no problem. I'll take it. Thanks! -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
