From: Steffen Klassert <steffen.klassert@secunet.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Mathias Krause <minipli@googlemail.com>,
Pan Bian <bianpan2016@163.com>,
"David S. Miller" <davem@davemloft.net>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Pan Bian <bianpan2013@163.com>
Subject: Re: [net] xfrm_user: use xfrm_state_put to free xfrm_state_alloc return value
Date: Tue, 27 Nov 2018 08:55:48 +0100 [thread overview]
Message-ID: <20181127075548.GK3581@gauss3.secunet.de> (raw)
In-Reply-To: <20181122144321.5gmyynui254qfeoq@gondor.apana.org.au>
On Thu, Nov 22, 2018 at 10:43:21PM +0800, Herbert Xu wrote:
> On Wed, Nov 21, 2018 at 09:09:23PM +0100, Mathias Krause wrote:
> >
> > -- >8 --
> >
> > Subject: [PATCH] xfrm_user: fix freeing of xfrm states on acquire
> >
> > Commit 565f0fa902b6 ("xfrm: use a dedicated slab cache for struct
> > xfrm_state") moved xfrm state objects to use their own slab cache.
> > However, it missed to adapt xfrm_user to use this new cache when
> > freeing xfrm states.
> >
> > Fix this by introducing and make use of a new helper for freeing
> > xfrm_state objects.
> >
> > Fixes: 565f0fa902b6 ("xfrm: use a dedicated slab cache for struct xfrm_state")
> > Reported-by: Pan Bian <bianpan2016@163.com>
> > Cc: <stable@vger.kernel.org> # v4.18+
> > Signed-off-by: Mathias Krause <minipli@googlemail.com>
>
> Acked-by: Herbert Xu <herbert@gondor.apana.org.au>
Applied, thanks everyone!
prev parent reply other threads:[~2018-11-27 7:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 6:57 [net] xfrm_user: use xfrm_state_put to free xfrm_state_alloc return value Pan Bian
2018-11-21 8:00 ` Herbert Xu
2018-11-21 20:09 ` Mathias Krause
2018-11-22 14:43 ` Herbert Xu
2018-11-27 7:55 ` Steffen Klassert [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=20181127075548.GK3581@gauss3.secunet.de \
--to=steffen.klassert@secunet.com \
--cc=bianpan2013@163.com \
--cc=bianpan2016@163.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=minipli@googlemail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.