Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1603641
| From | Linus Torvalds <torvalds@linux-foundation.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [x86] 45fc8757d1: BUG:unable_to_handle_kernel |
| Date | 2017-03-17 22:50 +0100 |
| Message-ID | <tm6vT-3sM-7@gated-at.bofh.it> (permalink) |
| References | <tlYRI-6bS-19@gated-at.bofh.it> <tm4kr-1GF-49@gated-at.bofh.it> <tm4u5-21N-5@gated-at.bofh.it> <tm4u6-21N-25@gated-at.bofh.it> <tm4Ns-29P-21@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Fri, Mar 17, 2017 at 11:20 AM, Andy Lutomirski <luto@kernel.org> wrote:
>
> I can easily imagine that breaking WINE or DOSEMU because it'll affect
> the LDT, too.
Can they even *read* the LDT contents, though? The whole accessed bit
doesn't show up in 'struct user_desc', so you can neither set it nor
read it.
> How about this:
I don't think that's _wrong_, but..
I'd really rather just do it in fill_ldt() itself, unless you can
explain how it would be visible to anybody..
Linus
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [x86] 45fc8757d1: BUG:unable_to_handle_kernel Linus Torvalds <torvalds@linux-foundation.org> - 2017-03-17 19:00 +0100
Re: [x86] 45fc8757d1: BUG:unable_to_handle_kernel Linus Torvalds <torvalds@linux-foundation.org> - 2017-03-17 19:10 +0100
Re: [x86] 45fc8757d1: BUG:unable_to_handle_kernel Linus Torvalds <torvalds@linux-foundation.org> - 2017-03-17 19:10 +0100
Re: [x86] 45fc8757d1: BUG:unable_to_handle_kernel Andy Lutomirski <luto@kernel.org> - 2017-03-17 19:30 +0100
Re: [x86] 45fc8757d1: BUG:unable_to_handle_kernel Andy Lutomirski <luto@amacapital.net> - 2017-03-17 21:20 +0100
Re: [x86] 45fc8757d1: BUG:unable_to_handle_kernel Linus Torvalds <torvalds@linux-foundation.org> - 2017-03-17 22:20 +0100
Re: [x86] 45fc8757d1: BUG:unable_to_handle_kernel Linus Torvalds <torvalds@linux-foundation.org> - 2017-03-17 22:50 +0100
csiph-web