Date: Fri, 03 Aug 2018 21:17:03 +0000 From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: "Oliver Pinter" <oliver.pinter@hardenedbsd.org> Cc: stable@freebsd.org Subject: Re: VNET related kernel panic on jail startup with epairs on 11-STABLE Message-ID: <20AA7D33-904F-494B-830F-59E09DC267E5@lists.zabbadoz.net> In-Reply-To: <CAPQ4ffsb=JK-4yXVQMugmL81gVJrNFHcYpMXePguy4YBiHYZvw@mail.gmail.com> References: <CAPQ4ffskA88vr-2nMCm37KhxZaYj3-XiZfcTPTFm8Dk5H7-%2BuQ@mail.gmail.com> <5428C6C5-5627-44DD-A4ED-AF28A305C4F4@lists.zabbadoz.net> <CAPQ4ffsb=JK-4yXVQMugmL81gVJrNFHcYpMXePguy4YBiHYZvw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3 Aug 2018, at 20:42, Oliver Pinter wrote: > On 8/3/18, Bjoern A. Zeeb <bzeeb-lists@lists.zabbadoz.net> wrote: >> On 3 Aug 2018, at 18:48, Oliver Pinter wrote: >> >>> Hi all! >>> >>> One of out users observed an VNET related kernel panic with epairs >>> in >>> a jail. Seems like some of the >> >> Well would be great for a start to (a) email virtualisation@ as well, >> (b) include a panic message, backtrace or other related information >> to >> deduce anything about the possible bug, (c) and not to conflate it >> with >> another totally unrelated MFC request. >> >> So what makes you think it’s related to tcp fast open? > > Every required detail is in HardenedBSD's github issue, but I copy the > kernel panic here: Ah sorry my bad; the issue said ZFS in the subject and I thought it refers to something else. Thanks! Looking at the backtrace it seems it is happening on teardown and not on startup but indeed in the fast open code and that PR 216613 indeed fixed this in head, good :) Hope Patrick will do the mfc for you. /bz
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20AA7D33-904F-494B-830F-59E09DC267E5>