On Fri, Jan 27, 2017 at 01:21:11PM +0100, Pablo Neira Ayuso wrote:
> 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:
> > >
> > > >
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
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
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