On Wednesday, August 17, 2022 2:50 AM, Borislav Petkov wrote: > On Wed, Aug 17, 2022 at 01:39:32AM +0000, Kani, Toshi wrote: > > Yes, but the impact is not necessarily limited to these modules. > > The impact is limited only to the modules which would otherwise > potentially load on a HP system which advertizes as "HPE ", "Server ". > > You're the only user of ghes_edac. So please state which drivers you > want blocked from loading on those platforms and where ghes_edac should > load instead. ghes_edac is used on Arm. This original issue happened on a non-HPE platform. I am not sure if this chipset-specific edac vs ghes_edac ordering issue is x86-specific. It may be safer to add the ghes check to edac_mc_add_mc_with_groups() to keep it protected from any edac driver. Toshi
