From: Greg KH <gregkh@linux-foundation.org>
To: maowenan <maowenan@huawei.com>
Cc: netdev@vger.kernel.org, dwmw2@infradead.org,
eric.dumazet@gmail.com, davem@davemloft.net,
stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH stable 4.4 V2 0/6] fix SegmentSmack in stable branch (CVE-2018-5390)
Date: Thu, 11 Oct 2018 16:07:35 +0200 [thread overview]
Message-ID: <20181011140735.GA9507@kroah.com> (raw)
In-Reply-To: <20180926202121.GB23881@kroah.com>
On Wed, Sep 26, 2018 at 10:21:21PM +0200, Greg KH wrote:
> On Tue, Sep 25, 2018 at 10:10:15PM +0800, maowenan wrote:
> > Hi Greg:
> >
> > can you review this patch set?
>
> It is still in the queue, don't worry. It will take some more time to
> properly review and test it.
>
> Ideally you could get someone else to test this and provide a
> "tested-by:" tag for it?
All now queued up, let's see what breaks :)
thanks,
greg k-h
next prev parent reply other threads:[~2018-10-11 14:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 8:24 [PATCH stable 4.4 V2 0/6] fix SegmentSmack in stable branch (CVE-2018-5390) Mao Wenan
2018-09-14 8:24 ` [PATCH stable 4.4 V2 1/6] tcp: increment sk_drops for dropped rx packets Mao Wenan
2018-09-14 8:24 ` [PATCH stable 4.4 V2 2/6] tcp: use an RB tree for ooo receive queue Mao Wenan
2018-09-14 8:24 ` [PATCH stable 4.4 V2 3/6] tcp: fix a stale ooo_last_skb after a replace Mao Wenan
2018-09-14 8:24 ` [PATCH stable 4.4 V2 4/6] tcp: free batches of packets in tcp_prune_ofo_queue() Mao Wenan
2018-09-14 8:24 ` [PATCH stable 4.4 V2 5/6] tcp: call tcp_drop() from tcp_data_queue_ofo() Mao Wenan
2018-09-14 8:24 ` [PATCH stable 4.4 V2 6/6] tcp: add tcp_ooo_try_coalesce() helper Mao Wenan
2018-09-25 14:10 ` [PATCH stable 4.4 V2 0/6] fix SegmentSmack in stable branch (CVE-2018-5390) maowenan
2018-09-26 20:21 ` Greg KH
2018-10-11 14:07 ` Greg KH [this message]
[not found] ` <CAPACB-yF16qtiYn9e41_iFNRUzHB349NEiAGubUvW-kiUwpRMQ@mail.gmail.com>
2018-10-12 3:39 ` maowenan
2018-10-12 3:53 ` Fwd: " salil GK
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=20181011140735.GA9507@kroah.com \
--to=gregkh@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=dwmw2@infradead.org \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maowenan@huawei.com \
--cc=netdev@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