From: Sasha Levin <sashal@kernel.org>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org,
Denis Andzakovic <denis.andzakovic@pulsesecurity.co.nz>,
Salvatore Bonaccorso <carnil@debian.org>,
Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH 3.16-4.14] tcp: Clear sk_send_head after purging the write queue
Date: Tue, 20 Aug 2019 09:27:45 -0400 [thread overview]
Message-ID: <20190820132745.GK30205@sasha-vm> (raw)
In-Reply-To: <41a61a2f87691d2bc839f26cdfe6f5ff2f51e472.camel@decadent.org.uk>
On Tue, Aug 20, 2019 at 03:11:37AM +0100, Ben Hutchings wrote:
>Sorry, this is the same issue that was already fixed by "tcp: reset
>sk_send_head in tcp_write_queue_purge". You can drop my version from
>the queue for 4.4 and 4.9 and revert it for 4.14.
I've fixed it up, thanks Ben.
--
Thanks,
Sasha
prev parent reply other threads:[~2019-08-20 13:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 11:53 [PATCH 3.16-4.14] tcp: Clear sk_send_head after purging the write queue Ben Hutchings
2019-08-13 18:33 ` Greg Kroah-Hartman
2019-08-20 2:11 ` Ben Hutchings
2019-08-20 13:27 ` 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=20190820132745.GK30205@sasha-vm \
--to=sashal@kernel.org \
--cc=ben@decadent.org.uk \
--cc=carnil@debian.org \
--cc=denis.andzakovic@pulsesecurity.co.nz \
--cc=edumazet@google.com \
--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 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).