From: Kenneth Porter <shiva@sewingwitch.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Red Hat kernel: Backport TCP follow-up for small buffers (BZ#1739130)
Date: Wed, 18 Sep 2019 15:02:16 -0700 [thread overview]
Message-ID: <39F71D63CF20EA5B5E1B6BAB@[192.168.1.16]> (raw)
I saw that intriguing "fix" in the latest Red Hat kernel errata but the
cited bugzilla isn't available to the public.
<https://access.redhat.com/errata/RHSA-2019:2600>
next reply other threads:[~2019-09-18 22:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 22:02 Kenneth Porter [this message]
2019-09-19 9:06 ` Toke Høiland-Jørgensen
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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='39F71D63CF20EA5B5E1B6BAB@[192.168.1.16]' \
--to=shiva@sewingwitch.com \
--cc=bloat@lists.bufferbloat.net \
/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