From: Steffen Klassert <steffen.klassert@secunet.com>
To: David Miller <davem@davemloft.net>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
Steffen Klassert <steffen.klassert@secunet.com>,
<netdev@vger.kernel.org>
Subject: pull request (net): ipsec 2019-11-13
Date: Wed, 13 Nov 2019 12:26:11 +0100 [thread overview]
Message-ID: <20191113112613.2596-1-steffen.klassert@secunet.com> (raw)
1) Fix a page memleak on xfrm state destroy.
2) Fix a refcount imbalance if a xfrm_state
gets invaild during async resumption.
From Xiaodong Xu.
Please pull or let me know if there are problems.
Thanks!
The following changes since commit 99a8efbb6e30b72ac98cecf81103f847abffb1e5:
NFC: st21nfca: fix double free (2019-11-06 21:48:29 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec.git master
for you to fetch changes up to 4944a4b1077f74d89073624bd286219d2fcbfce3:
xfrm: release device reference for invalid state (2019-11-12 08:24:38 +0100)
----------------------------------------------------------------
Steffen Klassert (1):
xfrm: Fix memleak on xfrm state destroy
Xiaodong Xu (1):
xfrm: release device reference for invalid state
net/xfrm/xfrm_input.c | 3 +++
net/xfrm/xfrm_state.c | 2 ++
2 files changed, 5 insertions(+)
next reply other threads:[~2019-11-13 11:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 11:26 Steffen Klassert [this message]
2019-11-13 11:26 ` [PATCH 1/2] xfrm: Fix memleak on xfrm state destroy Steffen Klassert
2019-11-13 11:26 ` [PATCH 2/2] xfrm: release device reference for invalid state Steffen Klassert
2019-11-13 19:26 ` pull request (net): ipsec 2019-11-13 David Miller
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=20191113112613.2596-1-steffen.klassert@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--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).