From: Sasha Levin <sashal@kernel.org>
To: Ben Hutchings <ben.hutchings@codethink.co.uk>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable <stable@vger.kernel.org>
Subject: Re: [stable] ipfrag: really prevent allocation on netns exit
Date: Sat, 26 Jan 2019 13:01:46 -0500 [thread overview]
Message-ID: <20190126180146.GC30183@sasha-vm> (raw)
In-Reply-To: <1548430288.3229.374.camel@codethink.co.uk>
On Fri, Jan 25, 2019 at 03:31:28PM +0000, Ben Hutchings wrote:
>Please pick this commit for the 4.9 and 4.14 stable branches:
>
>commit f6f2a4a2eb92bc73671204198bb2f8ab53ff59fb
>Author: Paolo Abeni <pabeni@redhat.com>
>Date: Fri Jul 6 12:30:20 2018 +0200
>
> ipfrag: really prevent allocation on netns exit
>
>It's not needed on earlier branches unless other commits are also applied.
Queued for 4.9 and 4.14, thank you.
--
Thanks,
Sasha
prev parent reply other threads:[~2019-01-26 18:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 15:31 [stable] ipfrag: really prevent allocation on netns exit Ben Hutchings
2019-01-26 18:01 ` Sasha Levin [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=20190126180146.GC30183@sasha-vm \
--to=sashal@kernel.org \
--cc=ben.hutchings@codethink.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=stable@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.