From owner-freebsd-stable@freebsd.org Wed Aug 12 22:15:49 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4654F99FBC5 for ; Wed, 12 Aug 2015 22:15:49 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 2ECAC7D4; Wed, 12 Aug 2015 22:15:49 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by freefall.freebsd.org (Postfix) with ESMTP id AD21C1834; Wed, 12 Aug 2015 22:15:48 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Wed, 12 Aug 2015 22:15:46 +0000 From: Glen Barber To: dweimer@dweimer.net Cc: FreeBSD Stable Subject: Re: Possible Error in the FreeBSD 10.2 Release Notes/Man page for TCP Message-ID: <20150812221546.GB1460@FreeBSD.org> References: <131f8a0f25200031103639e969702727@dweimer.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="0ntfKIWw70PvrIHh" Content-Disposition: inline In-Reply-To: <131f8a0f25200031103639e969702727@dweimer.net> X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Aug 2015 22:15:49 -0000 --0ntfKIWw70PvrIHh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 12, 2015 at 01:09:31PM -0500, dweimer wrote: > I was reading through the Release notes, and decided to enable > net.inet.tcp.pmtud_blackhole_detection in my test environment. It appears > that the monitoring tunable net.inet.tcp.pmtud_blackhole_min_activated is > incorrectly listed. Using sysctl -a | grep net.inet.tcp.pmtud, doesn't sh= ow > it as a result. The test system is running RC3 built on the 7th from > revision 286391 of the https://svn.freebsd.org/base/releng/10.2 tree. >=20 > root@freebsd:/usr/src # sysctl -a | grep net.inet.tcp.pmtud > net.inet.tcp.pmtud_blackhole_mss: 1200 > net.inet.tcp.pmtud_blackhole_failed: 0 > net.inet.tcp.pmtud_blackhole_activated_min_mss: 0 > net.inet.tcp.pmtud_blackhole_activated: 0 > net.inet.tcp.pmtud_blackhole_detection: 1 >=20 > I did confirm that the pmtud_blackhole_min_activated option is also listed > in the tcp(4) man page page as well. >=20 > If anyone is more familiar with this than I am can they look into seeing = if > there is indeed an error, or if I am missing something here. >=20 This appears to be an error based on the content of the commit log. I will confirm with the person that committed the code, and will note the findings in the 10.2-RELEASE errata document. Glen --0ntfKIWw70PvrIHh Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVy8WSAAoJEAMUWKVHj+KTsccQAIRB7L5kuEni7/FB2XXRAubt yurGalXpA2J/tWvT/yIO9r0X+yNCYCoUJ2D3jwCv9uVXEswDcmnHtQf++70Kpp12 eym/J0VCZq+tPdPmDsFux/FvF47fgkXJ33YUhFkM9MpD9+hbAQKtXV0Qqpm12MPh RakobsyHQQjliLX2K8rfADrwEzUqXXOtUW8kpcuzO7PzZH6sm/wLW0bdyfF61gNC eEDvGMTQUGg9WuYO4f3CXdXNAjTgvg8vqL3FYnM/sltr+k6rBoIGYNsqT6jSR2KP wvLCFYuO2jQlZ2hrn9gm/aItTrCB7cE5LFEoZWKHiASOB454q9XjAmqD5BSrJzol dsNb8qyRXY5VcQ8lPjVdOz4W2x9oqpxfySnNDj/ZvR/mSZ5Sh0DHXjP8dwOGtpJF 3XfHEYavPOjAJGbMksZurA61dzt+4RgceVze+/AzPp5DqQ/qbGK/PuP2WvD0kJOv JZOFRGWfRM5K2VMrtLhzaMqEXMJWGFAdqMJxfS7MLZtjMZq/pKad+prVfxlWvAff i50thV69WyXLkmmuDKz3ircXcuoalEmTSQZ8aEfNviLBBJY0YiiJgsE/Ieo3OKUT FRpfcFVeTzsWLvOYKgM+W6vTfQ+0PVRiupjp6iNOR3Qlt2exrr+APbCBbV6s0R8F tV7f9a4flXsMmlarM/ZW =TbzH -----END PGP SIGNATURE----- --0ntfKIWw70PvrIHh--