Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 27 Nov 2016 20:18:14 +0100
From:      Raphael Kubo da Costa <rakuco@FreeBSD.org>
To:        Baptiste Daroussin <bapt@FreeBSD.org>
Cc:        src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org
Subject:   Re: svn commit: r309194 - head/usr.sbin/syslogd
Message-ID:  <86shqchguh.fsf@FreeBSD.org>
In-Reply-To: <201611261550.uAQFo0HC074016@repo.freebsd.org> (Baptiste Daroussin's message of "Sat, 26 Nov 2016 15:50:00 %2B0000 (UTC)")
References:  <201611261550.uAQFo0HC074016@repo.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Baptiste Daroussin <bapt@FreeBSD.org> writes:

> Author: bapt
> Date: Sat Nov 26 15:49:59 2016
> New Revision: 309194
> URL: https://svnweb.freebsd.org/changeset/base/309194
>
> Log:
>   initialize *nextp which could be left uninitialized in case the configuration
>   file cannot be open/read
>
>   Reported by:	Coverity via cem
>   MFC after:	2 days
>   CID:		1365665

This is causing syslogd to crash on launch with SIGILL here (I'm on
r309213). The disassembly shows it's stumbling upon an UD2 instruction
here on amd64.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86shqchguh.fsf>