From: Gabriel Paubert <paubert@iram.es>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: Boot failure in 2.5.31 BK with new TLS patch
Date: Sat, 17 Aug 2002 20:26:56 +0200 [thread overview]
Message-ID: <3D5E9570.2090908@iram.es> (raw)
In-Reply-To: 200208171720.g7HHKim03809@localhost.localdomain
James Bottomley wrote:
>
>
> Actually, the intel manual recommends (but doesn't require) a wierd alignment
> for the descriptors. It recommends aligning them at an address which is 2 MOD
> 4 to avoid possible alignment check faults in user mode. Not that I think we
> can ever run into the problem, but we should probably obey the recommendation.
> I'll fix this up as well.
This is already done for the IDT descriptor, but not (yet) for the gdt
descriptor(s).
Alignment checks are only done when CPL==3. And lidt/lgdt are (obviously)
privileged, although sidt/sgdt (and sldt/str for that matter) are not,
but I can't see how application could take benefit or make malicious use
of this capability.
Gabriel.
next prev parent reply other threads:[~2002-08-17 18:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-17 0:31 Boot failure in 2.5.31 BK with new TLS patch James Bottomley
2002-08-17 6:51 ` Ingo Molnar
2002-08-17 15:16 ` James Bottomley
2002-08-17 16:17 ` Ingo Molnar
2001-11-02 8:20 ` Pavel Machek
2002-08-17 17:09 ` Gabriel Paubert
2002-08-17 17:18 ` Ingo Molnar
2002-08-17 17:20 ` James Bottomley
2002-08-17 18:26 ` Gabriel Paubert [this message]
2002-08-17 18:36 ` Linus Torvalds
2002-08-17 18:42 ` Ingo Molnar
2002-08-17 18:50 ` Gabriel Paubert
2002-08-17 18:53 ` Ingo Molnar
2002-08-17 21:42 ` Ingo Molnar
2002-08-18 3:29 ` Linus Torvalds
2002-08-17 22:34 ` James Bottomley
2002-08-18 8:35 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D5E9570.2090908@iram.es \
--to=paubert@iram.es \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox