Date: Thu, 19 Jan 2017 15:01:27 -0500 From: Shawn Webb <shawn.webb@hardenedbsd.org> To: Sean Bruno <sbruno@freebsd.org> Cc: peter.blok@bsd4all.org, freebsd-current@freebsd.org Subject: Re: crash in iflib_fast_intr Message-ID: <20170119200127.eo2fqaxx7gt7hwgx@mutt-hardenedbsd> In-Reply-To: <20170118194534.47vcuas7jllvw3o6@mutt-hardenedbsd> References: <0D6E88B3-6EB8-428F-B116-40D304CD74E5@bsd4all.org> <132b9c54-26dd-c57d-2fbb-58f8f9b256b0@freebsd.org> <20170118194534.47vcuas7jllvw3o6@mutt-hardenedbsd>
next in thread | previous in thread | raw e-mail | index | archive | help
--jut27mh3kgqfpavt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 18, 2017 at 02:45:34PM -0500, Shawn Webb wrote: > On Wed, Jan 18, 2017 at 07:31:12AM -0700, Sean Bruno wrote: > >=20 > >=20 > > On 01/18/17 03:37, peter.blok@bsd4all.org wrote: > > > Hi, > > >=20 > > > A kernel without option EARLY_AP_STARTUP crashes in if lib_fast_intr.= Since GENERIC now has EARLY_AP_STARTUP, this probably got unnoticed. Probl= em is reproducible. > > >=20 > > > KDB: stack backtrace: > > > #0 0xffffffff805cec97 at kdb_backtrace+0x67 > > > #1 0xffffffff80584816 at vpanic+0x186 > > > #2 0xffffffff80584683 at panic+0x43 > > > #3 0xffffffff8090f222 at trap_fatal+0x322 > > > #4 0xffffffff8090f3ec at trap_pfault+0x1bc > > > #5 0xffffffff8090eaa0 at trap+0x280 > > > #6 0xffffffff808f35e1 at calltrap+0x8 > > > #7 0xffffffff806a202d at iflib_fast_intr+0x3d > > > #8 0xffffffff8054963b at intr_event_handle+0x9b > > > #9 0xffffffff80965f38 at intr_execute_handlers+0x48 > > > #10 0xffffffff8096b1cf at lapic_handle_intr+0x3f > > > #11 0xffffffff808f3cc7 at Xapic_isr1+0xb7 > > > #12 0xffffffff805b994a at sched_idletd+0x37a > > > #13 0xffffffff805460f5 at fork_exit+0x85 > > > #14 0xffffffff808f3b1e at fork_trampoline+0xe > > >=20 > > > Peter > >=20 > > Thanks for the report. We're looking at this. > >=20 > > This is with an igb(4) interface or em(4)? > >=20 > > sean > >=20 >=20 > I'm getting something similar with em(4): >=20 > https://goo.gl/photos/MXiFXtatBYcWagJTA >=20 > I'm at this commit in HardenedBSD: >=20 > https://github.com/HardenedBSD/hardenedBSD/commit/2108b0d56984115eb52e72b= d16539071064b348e r312434 fixes this for me. Thanks a lot for the quick turnaround! --=20 Shawn Webb Cofounder and Security Engineer HardenedBSD GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE --jut27mh3kgqfpavt Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEKrq2ve9q9Ia+iT2eaoRlj1JFbu4FAliBGxUACgkQaoRlj1JF bu7eUg//SSIKVfop1qCRYoTqI1B2LKPJ7nhrjY5e/r377DFJVmnJ5HwOXlNlhnoT IgS7jKeY9pL95j5wKTpJSdIeP+EQp346gCy5xgLs9pDCfX3RSHt2SalzEtWNT24O Gr+FWliDHLisokh+MEumhgtG/J5KBaRChGxt7TwnGA6mfpAUGur5wU6iknvJEX// htTSOz+wG5wYy18PGd+rEpFhnGg+Ousar+tWkTqDwop+Cj3B6DiYvMKPKP3BogRe cZXAaEFDA+cMF0ArHcCWLZJyf11j8HUaqq8VlFQVsLI6UZwtV+5XBEzj7ZGAMrag ndeAWH/l0D8NB/jYq+MujgzDGAM9k0zUkKdWx8IM4mkO3qDC0fgi0tagTEy11+Ze PjKiChA0cmfj38+7JDghj1bUApwGHx7r01QOuB2yNJfaYxurdR94fh/AvMu28ekX zbEGXbwX9hrU8D+GDDYWbdtE28SgsjgzIByUZ04uGyGgZdauQCD7sNkLpyWw+0ON kCJ41nqLmbZhGYNIfj1XuiYoFpLW7B1VbFDnfhO7Jz7/qpY2gfV66JPN4QX8Wb7w rBZOAHS5ZZSCkMalx2a8qVjWsZDTDzslsRRL3m3ij8kVVNM1db9khyOmzty1/WS6 Fpbcww4hyMu4EwWztFTVyq8xgyDFNzJNi/mo3wKDYX8NYPtXhBg= =h9VC -----END PGP SIGNATURE----- --jut27mh3kgqfpavt--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170119200127.eo2fqaxx7gt7hwgx>