From: Greg KH <gregkh@linuxfoundation.org>
To: Paolo Abeni <pabeni@redhat.com>
Cc: davem@davemloft.net, stable@vger.kernel.org,
stable-commits@vger.kernel.org
Subject: Re: Patch "udp: perform source validation for mcast early demux" has been added to the 4.13-stable tree
Date: Mon, 9 Oct 2017 09:57:51 +0200 [thread overview]
Message-ID: <20171009075751.GA695@kroah.com> (raw)
In-Reply-To: <1507534651.2517.1.camel@redhat.com>
On Mon, Oct 09, 2017 at 09:37:31AM +0200, Paolo Abeni wrote:
> On Mon, 2017-10-09 at 09:35 +0200, gregkh@linuxfoundation.org wrote:
> > This is a note to let you know that I've just added the patch titled
> >
> > udp: perform source validation for mcast early demux
> >
> > to the 4.13-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > udp-perform-source-validation-for-mcast-early-demux.patch
> > and it can be found in the queue-4.13 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
>
> Please, keep this one on-hold. It needs a relevant follow-up I'm going
> to post soon!
Can I keep the patch before this one in the series "IPv4: early demux
can return an error code"? Or should I hold off on both of these for
now?
thanks,
greg k-h
next prev parent reply other threads:[~2017-10-09 7:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 7:35 Patch "udp: perform source validation for mcast early demux" has been added to the 4.13-stable tree gregkh
2017-10-09 7:37 ` Paolo Abeni
2017-10-09 7:57 ` Greg KH [this message]
2017-10-09 8:02 ` Paolo Abeni
2017-10-09 8:54 ` Greg KH
2017-10-10 7:16 ` Paolo Abeni
2017-10-10 7:31 ` Greg KH
2017-10-10 17:09 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2017-10-10 18:16 gregkh
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=20171009075751.GA695@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=pabeni@redhat.com \
--cc=stable-commits@vger.kernel.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 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).