Date: Sat, 17 Dec 2016 19:34:38 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 215356] smartmontools: fix panic on INVARIANTS enabled kernel after r308351 in base Message-ID: <bug-215356-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215356 Bug ID: 215356 Summary: smartmontools: fix panic on INVARIANTS enabled kernel after r308351 in base Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Keywords: patch Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: op@hardenedbsd.org CC: ken@FreeBSD.org, markj@FreeBSD.org Flags: maintainer-feedback+, merge-quarterly? Created attachment 178032 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D178032&action= =3Dedit 0001-smartmontools-fix-panic-on-INVARIANTS-enabled-kernel.patch smartmontools: fix panic on INVARIANTS enabled kernel after r308351 in base After r308351 commit the INVARIANTS enabled kernel gets too "eager" when checking the cam ccb flags. But the real problem was not the previous, = but the smartmontools does not zeroed out the ccb on stack, and pass this dirty ccb to kernel, which is catched by an ASSERT. So fix this by fill= ing up with 0 this ccb. This commit is similar, what's happen in r307684 in camcontrol. So this is the same followup patch in smartmontools. https://svnweb.freebsd.org/base?view=3Drevision&revision=3D307684 https://svnweb.freebsd.org/base?view=3Drevision&revision=3D308351 Sponsored-by: opBSD --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-215356-13>