[<prev] [next>] [day] [month] [year] [list]
Message-ID: <8378.1567269933@warthog.procyon.org.uk>
Date: Sat, 31 Aug 2019 17:45:33 +0100
From: David Howells <dhowells@...hat.com>
To: Hillf Danton <hdanton@...a.com>
Cc: dhowells@...hat.com, netdev@...r.kernel.org,
marc.dionne@...istor.com, linux-afs@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net] rxrpc: Fix lack of conn cleanup when local endpoint is cleaned up [ver #2]
Hillf Danton <hdanton@...a.com> wrote:
> > - if (rxnet->live) {
> > + if (rxnet->live && !conn->params.local->dead) {
> > idle_timestamp = READ_ONCE(conn->idle_timestamp);
> > expire_at = idle_timestamp + rxrpc_connection_expiry * HZ;
> > if (conn->params.local->service_closed)
>
> Is there any chance out there that this reaper starts running one minute
> after the dead local went into graveyard?
It's certainly possible that that can happen. The reaper is per
network-namespace.
conn->params.local holds a ref on the local endpoint.
It may be worth wrapping the "local->dead = true;" in rxrpc_local_destroyer()
in rxnet->conn_lock.
David
Powered by blists - more mailing lists