lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49F442796158E773+c51253ff-8051-4c25-9c95-e5305d13628b@uniontech.com>
Date: Wed, 31 Jul 2024 11:58:35 +0800
From: WangYuli <wangyuli@...ontech.com>
To: "Huang, Kai" <kai.huang@...el.com>, "seanjc@...gle.com"
 <seanjc@...gle.com>
Cc: "baimingcong@...ontech.com" <baimingcong@...ontech.com>,
 "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
 "linux-sgx@...r.kernel.org" <linux-sgx@...r.kernel.org>,
 "bp@...en8.de" <bp@...en8.de>,
 "dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
 "jarkko@...nel.org" <jarkko@...nel.org>, "hpa@...or.com" <hpa@...or.com>,
 "tglx@...utronix.de" <tglx@...utronix.de>, "x86@...nel.org"
 <x86@...nel.org>, "mingo@...hat.com" <mingo@...hat.com>,
 "xiangzelong@...ontech.com" <xiangzelong@...ontech.com>,
 "wubo@...ontech.com" <wubo@...ontech.com>,
 "guanwentao@...ontech.com" <guanwentao@...ontech.com>,
 "haitao.huang@...ux.intel.com" <haitao.huang@...ux.intel.com>
Subject: Re: [PATCH] x86/cpufeatures: SGX: Adjust the error message when BIOS
 does not support SGX

On 2024/7/31 06:48, Huang, Kai wrote:

>> FWIW, this could easily happen with a virtual machine, e.g. running an old QEMU
>> with `-cpu host`.
>>
> Hmm.. it appears so, if the old Qemu doesn't have SGX support.  Thanks.
>
> Perhaps "SGX disabled or unsupported by BIOS." or "SGX not enabled by
> BIOS" is slightly better than the current "SGX disabled by BIOS", but I
> am not sure whether it is worth patching.

Of course, most kernel developers are incredibly busy and are reluctant 
to spend their time

on those little changes.


However, the user base of Linux is gradually shifting from 
'professionals' to 'general users'.

As I mentioned in the commit msg. I hope to make kernel logs clearer and 
more understandable,

reducing confusion for those who are unfamiliar with the codebase.


It's important that any change in upstream can potentially impact 
countless users.


Sincerely,

-- 
WangYuli


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ