On 10/27/13 at 08:30pm, Matt Fleming wrote: > On Sun, 27 Oct, at 11:50:09AM, Borislav Petkov wrote: > > On Sun, Oct 27, 2013 at 11:47:15AM +0800, dyoung@xxxxxxxxxx wrote: > > > Current code check boot service region with kernel text region by: > > > start+size >= __pa_symbol(_text) > > > The end of the above region should be start + size - 1 instead. > > > > > > I see this problem in ovmf + Fedora 19 grub boot: > > > text start: 1000000 md start: 800000 md size: 800000 > > > > > > Signed-off-by: Dave Young <dyoung@xxxxxxxxxx> > > > > Acked-by: Borislav Petkov <bp@xxxxxxx> > > > > Btw, Matt, this being a bugfix and all, shouldn't it be tagged for > > stable? > > Well that depends. Dave, am I correct in thinking that you only noticed > this bug when writing kexec support? I'm inclined not to bother with a > stable tag if no one has ever noticed any fallout from this bug until > now. There should be some people see below message with non-kexec kernel: "Could not reserve boot range ..." But it's hard for them to notice the bad functionality because it's only one mem range which might be not the boot range what SetVirtualAddressMap need -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
