On Wed, 2017-05-10 at 23:57 +0200, Borislav Petkov wrote: > On Wed, May 10, 2017 at 09:12:12PM +0000, Verma, Vishal L wrote: > > The memory error check in the nfit handler is a valid, and simple > > fix. > > I need the big picture here: "Without this fix, the nfit handler ...". ..will potentially add bogus address to an 'error list', even when there may not have been a memory error. (can mce->addr have an address when the mce is not due to a memory error?) The result of adding an address to this list is that future accesses to this location will prematurely error out. Depending on how frequently machine checks happen that are not memory errors but have the addr field set (hopefully rare anyway), we could be incorrectly marking a lot of locations as media errors. > > Then, if the stable rules apply, we can always expedite it through > urgent/stable. >