From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:50832)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <armbru@pond.sub.org>) id 1X2Gse-0007MS-Kj
	for qemu-devel@nongnu.org; Wed, 02 Jul 2014 05:31:17 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <armbru@pond.sub.org>) id 1X2GsV-00077I-JA
	for qemu-devel@nongnu.org; Wed, 02 Jul 2014 05:31:08 -0400
Received: from oxygen.pond.sub.org ([2a01:4f8:201:233:1::3]:44253)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <armbru@pond.sub.org>) id 1X2GsV-00077C-CA
	for qemu-devel@nongnu.org; Wed, 02 Jul 2014 05:30:59 -0400
Received: from blackfin.pond.sub.org (p5B328159.dip0.t-ipconnect.de
	[91.50.129.89])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client did not present a certificate)
	by oxygen.pond.sub.org (Postfix) with ESMTPSA id B12A4259EE
	for <qemu-devel@nongnu.org>; Wed,  2 Jul 2014 11:30:57 +0200 (CEST)
From: Markus Armbruster <armbru@redhat.com>
References: <1404288324-16766-1-git-send-email-mrezanin@redhat.com>
Date: Wed, 02 Jul 2014 11:30:56 +0200
In-Reply-To: <1404288324-16766-1-git-send-email-mrezanin@redhat.com>
	(mrezanin@redhat.com's message of "Wed, 2 Jul 2014 10:05:24 +0200")
Message-ID: <871tu46ran.fsf@blackfin.pond.sub.org>
MIME-Version: 1.0
Content-Type: text/plain
Subject: Re: [Qemu-devel] [PATCH] Enforce stack protector usage
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: mrezanin@redhat.com
Cc: qemu-devel@nongnu.org

mrezanin@redhat.com writes:

> From: Miroslav Rezanina <mrezanin@redhat.com>
>
> If --enable-stack-protector is used is used, configure script try to use
> --fstack-protector-strong. In case it's not supported, --fstack-protector-all
> is enabled. If both protectors are not supported, configure does not use
> any protector at all without any notification.
>
> This patch reports error when user requests stack protector to be used and
> both protector modes are not supported. Behavior is not changed in case
> user do not use any of --enable-stack-protector/--disable-stack-protector.
>
> Signed-off-by: Miroslav Rezanina <mrezanin@redhat.com>

Reviewed-by: Markus Armbruster <armbru@redhat.com>