From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wtarreau.pck.nerim.net ([62.212.114.60]:44969 "EHLO 1wt.eu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725826AbeKSIYr (ORCPT ); Mon, 19 Nov 2018 03:24:47 -0500 Date: Sun, 18 Nov 2018 22:59:30 +0100 From: Willy Tarreau To: Jiri Kosina Cc: Linus Torvalds , Thomas Gleixner , Peter Zijlstra , Josh Poimboeuf , Andrea Arcangeli , David Woodhouse , Andi Kleen , Tim Chen , Casey Schaufler , Linux List Kernel Mailing , the arch/x86 maintainers , stable@vger.kernel.org Subject: Re: STIBP by default.. Revert? Message-ID: <20181118215930.GA11126@1wt.eu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: stable-owner@vger.kernel.org List-ID: On Sun, Nov 18, 2018 at 10:49:44PM +0100, Jiri Kosina wrote: > odds are that people > who don't care about spectrev2 already have 'nospectre_v2' on their > command-line, so they are fine as well. FWIW in our appliances, we never modify the boot loader's cmdline in field, we only provide new kernel+rootfs images. We've however disabled the config options for all this class of vulnerabilities. As long as it remains possible to disable the new ones using config options only, that's not an issue for me. Cheers, Willy