From: David Miller <davem@davemloft.net>
To: dhowells@redhat.com
Cc: netdev@vger.kernel.org, linux-afs@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] rxrpc: Fix a missing rxrpc_put_peer() in the error_report handler
Date: Mon, 15 Oct 2018 23:14:47 -0700 (PDT) [thread overview]
Message-ID: <20181015.231447.86687598764526168.davem@davemloft.net> (raw)
In-Reply-To: <153963944115.2618.17691876338723925930.stgit@warthog.procyon.org.uk>
From: David Howells <dhowells@redhat.com>
Date: Mon, 15 Oct 2018 22:37:21 +0100
> Fix a missing call to rxrpc_put_peer() on the main path through the
> rxrpc_error_report() function. This manifests itself as a ref leak
> whenever an ICMP packet or other error comes in.
>
> In commit f334430316e7, the hand-off of the ref to a work item was removed
> and was not replaced with a put.
>
> Fixes: f334430316e7 ("rxrpc: Fix error distribution")
> Signed-off-by: David Howells <dhowells@redhat.com>
Applied.
prev parent reply other threads:[~2018-10-16 6:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 21:37 [PATCH net] rxrpc: Fix a missing rxrpc_put_peer() in the error_report handler David Howells
2018-10-16 6:14 ` David Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181015.231447.86687598764526168.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox