From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755765AbcARPmp (ORCPT ); Mon, 18 Jan 2016 10:42:45 -0500 Received: from unicorn.mansr.com ([81.2.72.234]:45117 "EHLO unicorn.mansr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755594AbcARPmk convert rfc822-to-8bit (ORCPT ); Mon, 18 Jan 2016 10:42:40 -0500 From: =?iso-8859-1?Q?M=E5ns_Rullg=E5rd?= To: Borislav Petkov Cc: Thomas Voegtle , Michal Marek , Markus Trippelsdorf , linux-kernel@vger.kernel.org, x86-ml Subject: Re: [RFC PATCH] x86/kconfig: Sanity-check config file during oldconfig References: <20160111205945.GH4686@pd.tnic> <20160111211712.GI4686@pd.tnic> <20160114184350.GB12109@pd.tnic> <20160118140649.GC12651@pd.tnic> <20160118144114.GE12651@pd.tnic> <20160118153941.GF12651@pd.tnic> Date: Mon, 18 Jan 2016 15:42:32 +0000 In-Reply-To: <20160118153941.GF12651@pd.tnic> (Borislav Petkov's message of "Mon, 18 Jan 2016 16:39:41 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Borislav Petkov writes: > On Mon, Jan 18, 2016 at 02:51:00PM +0000, Måns Rullgård wrote: >> I understand and disagree. I think you're being overzealous in trying >> to bludgeon people into doing things the way you think they should be >> done. > > So I did explain why it is better to do microcode updates from the > initrd. And nowhere in that explanation I am "bludgeoning" people into > doing things the way I want. Which is silly, I'd never even *think* of > wanting to do that - I have enough other shit to deal with. Forcing users to press a damn key on the keyboard after your pointless warning message sure feels like bludgeoning to me. >> From the point of view of the actual update mechanism, what difference >> does it make where the microcode data was retrieved from? If you want >> to warn about what you consider "unsafe" updates, do that when the >> update happens instead. With this patch, simply enabling BLK_DEV_INITRD >> will shut up the warning even if an initrd is never actually used. >> Also, what do modules have to do with anything? > > This reads like your mail from a couple of days ago. Which leads me to > think that you haven't understood at all what I've been writing this > whole time. Clearly you didn't explain it very well. -- Måns Rullgård