All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: sashal@kernel.org
Cc: captwiggum@gmail.com, posk@google.com,
	gregkh@linuxfoundation.org, stable@vger.kernel.org,
	netdev@vger.kernel.org, posk@posk.io, edumazet@google.com
Subject: Re: [PATCH 4.19 stable 0/3] net: ip6 defrag: backport fixes
Date: Fri, 19 Apr 2019 11:55:11 -0700 (PDT)	[thread overview]
Message-ID: <20190419.115511.199810045244145455.davem@davemloft.net> (raw)
In-Reply-To: <20190417205317.GG435@sasha-vm>

From: Sasha Levin <sashal@kernel.org>
Date: Wed, 17 Apr 2019 16:53:17 -0400

> On Wed, Apr 17, 2019 at 11:51:27AM -0600, Captain Wiggum wrote:
>>Hi All,
>>
>>We have built 4.19 with Peter's patch, and now all TAHI IPv6 tests
>>pass, even another issue I reported is fixed!
>>This patch looks great from our testing. Please accept this patch...
>>So that Peter can move on to 4.14.
>>Thank you Peter and Google crew for this patch!
>>I look forward to the fix for 4.14, and then 4.9.
> 
> This will need to go through David Miller (or at least acked by him)
> for
> 4.19.

It is a set of reasonably non-trivial changes, however since it fixes
fundamental issues and has had testing, I'm ok with this going into v4.19:

Acked-by: David S. Miller <davem@davemloft.net>

  reply	other threads:[~2019-04-19 18:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09  0:10 [PATCH 4.19 stable 0/3] net: ip6 defrag: backport fixes Peter Oskolkov
2019-04-09  0:10 ` [PATCH 4.19 stable 1/3] net: IP defrag: encapsulate rbtree defrag code into callable functions Peter Oskolkov
2019-04-09  0:10 ` [PATCH 4.19 stable 2/3] net: IP6 defrag: use rbtrees for IPv6 defrag Peter Oskolkov
2019-04-09  0:10 ` [PATCH 4.19 stable 3/3] net: IP6 defrag: use rbtrees in nf_conntrack_reasm.c Peter Oskolkov
2019-04-14 18:28 ` [PATCH 4.19 stable 0/3] net: ip6 defrag: backport fixes Captain Wiggum
2019-04-17 17:51   ` Captain Wiggum
2019-04-17 20:53     ` Sasha Levin
2019-04-19 18:55       ` David Miller [this message]
2019-04-22  0:42         ` Sasha Levin

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=20190419.115511.199810045244145455.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=captwiggum@gmail.com \
    --cc=edumazet@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=netdev@vger.kernel.org \
    --cc=posk@google.com \
    --cc=posk@posk.io \
    --cc=sashal@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 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.