Date: Mon, 24 Sep 2018 23:24:53 +0300 From: "Andrey V. Elsukov" <bu7cher@yandex.ru> To: "John W. O'Brien" <john@saltant.com>, FreeBSD Net <freebsd-net@freebsd.org> Cc: Xin LI <delphij@gmail.com>, Kristof Provost <kp@FreeBSD.org> Subject: Re: IPv6 fragment reassembly regression following FreeBSD-SA-18:10.ip Message-ID: <d0f80022-eb1b-cfb3-b349-3c71d4c24d87@yandex.ru> In-Reply-To: <38a2d322-eae9-ec3d-284c-af29aed10c03@saltant.com> References: <38a2d322-eae9-ec3d-284c-af29aed10c03@saltant.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --5giEUYRIsfJDyYdsPmznPzCUyh4JR9xc9 Content-Type: multipart/mixed; boundary="lwDs4zUOTGzmx8wEfmz02BpKlf1I9ja0X"; protected-headers="v1" From: "Andrey V. Elsukov" <bu7cher@yandex.ru> To: "John W. O'Brien" <john@saltant.com>, FreeBSD Net <freebsd-net@freebsd.org> Cc: Xin LI <delphij@gmail.com>, Kristof Provost <kp@FreeBSD.org> Message-ID: <d0f80022-eb1b-cfb3-b349-3c71d4c24d87@yandex.ru> Subject: Re: IPv6 fragment reassembly regression following FreeBSD-SA-18:10.ip References: <38a2d322-eae9-ec3d-284c-af29aed10c03@saltant.com> In-Reply-To: <38a2d322-eae9-ec3d-284c-af29aed10c03@saltant.com> --lwDs4zUOTGzmx8wEfmz02BpKlf1I9ja0X Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 23.09.2018 16:43, John W. O'Brien wrote: > I'd like to check my understanding and then ask a procedural question. >=20 > FreeBSD-SA-18:10.ip [0], released on 08/14, was resolved by r337828 [1]= =2E > That changeset, resulting in 11.1R-p13 and 11.2R-p2, included a patch t= o > the way IPv6 fragment reassembly is handled [2] that was part of the > merge to releng. In an ensuing thread [3] two weeks later, an > implementation defect was identified, but not before that defect had > shipped. The defect is now being tracked as a bug [4], as of 09/03 has > been fixed in head and stable/11, and is registered as a blocker for 12= =2E0. >=20 > I believe this defect is the cause of a problem I detected recently > where postfix would query BIND on ::1 for the DNSSEC-signed AAAA of an > MX, and never receive a response. I'm a little puzzled that lo0 is > affected in spite of having a 16k MTU, but the other signs are there: > the symptoms appeared after upgrading from 11.2R-p1 to -p3, and I can > perform that query successfully on UDPv4 or TCPv6. >=20 > What I have been unable so far to determine is, will another 11.2R patc= h > be forthcoming to resolve this regression, and if so, when? I can limp > along without UDPv6 for a little while, but not until 11.3. The only > clear alternative is to downgrade to -p1. >=20 > [0] https://www.freebsd.org/security/advisories/FreeBSD-SA-18:10.ip.asc= > [1] https://svnweb.freebsd.org/changeset/base/337828 > [2] https://svnweb.freebsd.org/changeset/base/337776 > [3] https://lists.freebsd.org/pipermail/svn-src-head/2018-August/117514= =2Ehtml > [4] https://bugs.freebsd.org/231045 Your analysis looks correct to me. r338406 was not merged to releng/11.2.= --=20 WBR, Andrey V. Elsukov --lwDs4zUOTGzmx8wEfmz02BpKlf1I9ja0X-- --5giEUYRIsfJDyYdsPmznPzCUyh4JR9xc9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAlupSBUACgkQAcXqBBDI oXr0vwf/T2sFwS0SzFvxButAjV/fvsROasVUg4tipNo3tnnERHqthDOi5008we0i FcTJHZ+k8hzmdDyo0mz1LbllMcim/TiUyOexbn8/+ME3XAuEMzq92q4gbDty4d+T K0Zthl64axwe7phLF2jMcAgU9HYOuqsEVpv5WlvEQk5c8tZPWTfFr5SUt4ETjMMR QPW8+UyHVhVlOXtXpyoPQL8c2Kmy8NTJFX28OjSPelHqsBZRmnhQzOJ7WYbiYNiE SPISQaDhMnUyCgAe5mw7yCGtjRLjNoi1pVFbiLJooRQyCiZz7OAnc4BrTZjsiuFt x5ygVErrcE+BnF3uTINlUJiVjIIRGg== =oI2P -----END PGP SIGNATURE----- --5giEUYRIsfJDyYdsPmznPzCUyh4JR9xc9--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d0f80022-eb1b-cfb3-b349-3c71d4c24d87>