From: David Howells <dhowells@redhat.com>
To: netdev@vger.kernel.org
Cc: dhowells@redhat.com, linux-afs@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH net 0/2] rxrpc: Fix a warning and a leak
Date: Sat, 23 May 2020 00:23:21 +0100 [thread overview]
Message-ID: <159018980141.996784.14747585629466633699.stgit@warthog.procyon.org.uk> (raw)
Here are a couple of fixes for AF_RXRPC:
(1) Fix an uninitialised variable warning.
(2) Fix a leak of the ticket on error in rxkad.
The patches are tagged here:
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
rxrpc-fixes-20200523
and can also be found on the following branch:
http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=rxrpc-fixes
and follows on from rxrpc-fixes-20200521.
David
---
Qiushi Wu (1):
A ticket was not released after a call of the function
fs/afs/fs_probe.c | 18 ++--
fs/afs/vl_probe.c | 18 ++--
include/net/af_rxrpc.h | 2 +-
include/trace/events/rxrpc.h | 52 +++++++++---
net/rxrpc/Makefile | 1 +
net/rxrpc/ar-internal.h | 25 ++++--
net/rxrpc/call_accept.c | 2 +-
net/rxrpc/call_event.c | 22 ++---
net/rxrpc/input.c | 44 ++++++++--
net/rxrpc/misc.c | 5 --
net/rxrpc/output.c | 9 +-
net/rxrpc/peer_event.c | 46 ----------
net/rxrpc/peer_object.c | 12 +--
net/rxrpc/proc.c | 8 +-
net/rxrpc/rtt.c | 195 +++++++++++++++++++++++++++++++++++++++++++
net/rxrpc/rxkad.c | 3 +-
net/rxrpc/sendmsg.c | 26 ++----
net/rxrpc/sysctl.c | 9 --
18 files changed, 336 insertions(+), 161 deletions(-)
create mode 100644 net/rxrpc/rtt.c
next reply other threads:[~2020-05-22 23:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 23:23 David Howells [this message]
2020-05-22 23:23 ` [PATCH net 1/2] rxrpc: Fix a warning David Howells
2020-05-22 23:23 ` [PATCH net 2/2] A ticket was not released after a call of the function David Howells
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=159018980141.996784.14747585629466633699.stgit@warthog.procyon.org.uk \
--to=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;
as well as URLs for NNTP newsgroup(s).