The F00F big just means the IDT must be readonly. Steven Rostedt <rost...@goodmis.org> wrote:
>On Tue, 2013-07-16 at 13:28 -0700, Kees Cook wrote: >> On Tue, Jul 16, 2013 at 1:21 PM, Yinghai Lu <ying...@kernel.org> >wrote: >> > On Tue, Jul 16, 2013 at 11:34 AM, Kees Cook <keesc...@chromium.org> >wrote: >> >> Since the IDT is referenced from a fixmap, make sure it is page >aligned. >> >> Merge with 32-bit one, since it was already aligned to deal with >F00F >> >> bug. Since bss is cleared before IDT setup, it can live there. >This also >> >> moves the other *_idt_table variables into common locations. >> >> > >> It seemed more correct to me to define all the IDTs the same, but >> there was no technical reason for that, just one of regularity. I >only >> care about keeping the real IDT page aligned. :) I'm fine to do >> whatever is deemed "correct". :) > >I'm actually unfamiliar with the F00F bug (heard of it, but have no >idea >what it is). What happens if the F00F bug exists and we switch to an >IDT >that's not paged aligned? Is that an issue? > >-- Steve -- Sent from my mobile phone. Please excuse brevity and lack of formatting. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
