From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754768AbcAHLgu (ORCPT ); Fri, 8 Jan 2016 06:36:50 -0500 Received: from mx2.suse.de ([195.135.220.15]:60466 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754358AbcAHLgt (ORCPT ); Fri, 8 Jan 2016 06:36:49 -0500 Date: Fri, 8 Jan 2016 12:36:41 +0100 From: Borislav Petkov To: =?utf-8?B?TcOlbnMgUnVsbGfDpXJk?= Cc: Thomas Voegtle , Markus Trippelsdorf , linux-kernel@vger.kernel.org Subject: Re: x86/microcode update on systems without INITRD Message-ID: <20160108113641.GE14673@pd.tnic> References: <20151119214301.GA318@x4> <20151119215543.GA4926@pd.tnic> <20151119225828.GB4926@pd.tnic> <20151120071920.GA321@x4> <20151120082716.GA4028@pd.tnic> <20160107121841.GB16472@pd.tnic> <20160108105900.GA14673@pd.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jan 08, 2016 at 11:18:51AM +0000, Måns Rullgård wrote: > Neither "depends on" nor "select" makes sense to me here. The driver > apparently works without it, The driver works without it if you build your microcode into the kernel. There are use cases where building microcode into the kernel is *not* a viable option so we have to support both builtin microcode and microcode from the initrd. > and simply having BLK_DEV_INITRD enabled doesn't prevent improper > (according to some people) use of the driver. If updating microcode > is inherently unsafe when a real disk is mounted, the driver ought > to detect this and refuse the operation (possibly with an override > option). Huh, what? -ENOPARSE. -- Regards/Gruss, Boris. SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) --