From: Willy Tarreau <w@1wt.eu>
To: davem@davemloft.net
Cc: yongjian xu <yongjianchn@gmail.com>,
Soheil Hassas Yeganeh <soheil.kdev@gmail.com>,
netdev@vger.kernel.org, ycheng@google.com, ncardwell@google.com,
nefelim4ag@gmail.com, Soheil Hassas Yeganeh <soheil@google.com>,
Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH linux-stable-4.14] tcp: reset sk_send_head in tcp_write_queue_purge
Date: Tue, 20 Mar 2018 17:13:31 +0100 [thread overview]
Message-ID: <20180320161331.GA31452@1wt.eu> (raw)
In-Reply-To: <CACrmbvZzCvO6pTpvq=mE54s3CwAaBB4npc+E7Fa8zvMArL3t7A@mail.gmail.com>
Hi David,
regarding the patch below, I'm not certain whether you planned to take
it since it's marked "not applicable" on patchwork, but I suspect it's
only because it doesn't apply to mainline.
However, please note that there are two typos in commit IDs referenced in
the commit message that might be nice to fix before merging :
> > For example, after 27fid7a8ed38 (tcp: purge write queue upon RST),
- here it's "a27fd7a8ed38" (missing 'a' and extra 'i' in the middle)
- and lower in the fixes tag there's the extra 'i' as well :
> > Fixes: a27fid7a8ed38 (tcp: purge write queue upon RST)
There was another report today on the stable list for a similar crash
on 4.14.28 and I suspect it's the one I saw this week-end on my firewall
after upgrading from 4.14.10 to 4.14.27 though I didn't have the symbols
to confirm.
Thanks,
Willy
next prev parent reply other threads:[~2018-03-20 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 16:09 [PATCH linux-stable-4.14] tcp: reset sk_send_head in tcp_write_queue_purge Soheil Hassas Yeganeh
2018-03-16 14:26 ` yongjian xu
2018-03-20 16:13 ` Willy Tarreau [this message]
2018-03-29 10:00 ` Timofey Titovets
2018-03-29 10:09 ` Jack Wang
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=20180320161331.GA31452@1wt.eu \
--to=w@1wt.eu \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ncardwell@google.com \
--cc=nefelim4ag@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=soheil.kdev@gmail.com \
--cc=soheil@google.com \
--cc=ycheng@google.com \
--cc=yongjianchn@gmail.com \
/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.