From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Andy Lutomirski <luto@amacapital.net>
Cc: "security@kernel.org" <security@kernel.org>,
Peter Zijlstra <peterz@infradead.org>, X86 ML <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
xen-devel <xen-devel@lists.xen.org>,
Borislav Petkov <bp@alien8.de>, Jan Beulich <jbeulich@suse.com>,
Sasha Levin <sasha.levin@oracle.com>
Subject: Re: [Xen-devel] [PATCH v4 0/3] x86: modify_ldt improvement, test, and config option
Date: Tue, 28 Jul 2015 23:01:19 -0400 [thread overview]
Message-ID: <55B841FF.2000102@oracle.com> (raw)
In-Reply-To: <55B822B8.3090608@citrix.com>
On 07/28/2015 08:47 PM, Andrew Cooper wrote:
> On 29/07/2015 01:21, Andy Lutomirski wrote:
>> On Tue, Jul 28, 2015 at 10:10 AM, Boris Ostrovsky
>> <boris.ostrovsky@oracle.com> wrote:
>>> On 07/28/2015 01:07 PM, Andy Lutomirski wrote:
>>>> On Tue, Jul 28, 2015 at 9:30 AM, Andrew Cooper
>>>> <andrew.cooper3@citrix.com> wrote:
>>>>> I suspect that the set_ldt(NULL, 0) call hasn't reached Xen before
>>>>> xen_free_ldt() is attempting to nab back the pages which Xen still has
>>>>> mapped as an LDT.
>>>>>
>>>> I just instrumented it with yet more LSL instructions. I'm pretty
>>>> sure that set_ldt really is clearing at least LDT entry zero.
>>>> Nonetheless the free_ldt call still oopses.
>>>>
>>> Yes, I added some instrumentation to the hypervisor and we definitely set
>>> LDT to NULL before failing.
>>>
>>> -boris
>> Looking at map_ldt_shadow_page: what keeps shadow_ldt_mapcnt from
>> getting incremented once on each CPU at the same time if both CPUs
>> fault in the same shadow LDT page at the same time?
> Nothing, but that is fine. If a page is in use in two vcpus LDTs, it is
> expected to have a type refcount of 2.
>
>> Similarly, what
>> keeps both CPUs from calling get_page_type at the same time and
>> therefore losing track of the page type reference count?
> a cmpxchg() loop in the depths of __get_page_type().
>
>> I don't see why vmalloc or vm_unmap_aliases would have anything to do
>> with this, though.
So just for kicks I made lazy_max_pages() return 0 to free vmaps
immediately and the problem went away.
I also saw this warning, BTW:
[ 178.686542] ------------[ cut here ]------------
[ 178.686554] WARNING: CPU: 0 PID: 16440 at
./arch/x86/include/asm/mmu_context.h:96 load_mm_ldt+0x70/0x76()
[ 178.686558] DEBUG_LOCKS_WARN_ON(!irqs_disabled())
[ 178.686561] Modules linked in:
[ 178.686566] CPU: 0 PID: 16440 Comm: kworker/u2:1 Not tainted
4.1.0-32b #80
[ 178.686570] 00000000 00000000 ea4e3df8 c1670e71 00000000 ea4e3e28
c106ac1e c1814e43
[ 178.686577] ea4e3e54 00004038 c181bc2c 00000060 c166fd3b c166fd3b
e6705dc0 00000000
[ 178.686583] ea665000 ea4e3e40 c106ad03 00000009 ea4e3e38 c1814e43
ea4e3e54 ea4e3e5c
[ 178.686589] Call Trace:
[ 178.686594] [<c1670e71>] dump_stack+0x41/0x52
[ 178.686598] [<c106ac1e>] warn_slowpath_common+0x8e/0xd0
[ 178.686602] [<c166fd3b>] ? load_mm_ldt+0x70/0x76
[ 178.686609] [<c166fd3b>] ? load_mm_ldt+0x70/0x76
[ 178.686612] [<c106ad03>] warn_slowpath_fmt+0x33/0x40
[ 178.686615] [<c166fd3b>] load_mm_ldt+0x70/0x76
[ 178.686619] [<c11ad5e9>] flush_old_exec+0x6f9/0x750
[ 178.686626] [<c11efb54>] load_elf_binary+0x2b4/0x1040
[ 178.686630] [<c1173785>] ? page_address+0x15/0xf0
[ 178.686633] [<c106466f>] ? kunmap+0x1f/0x70
[ 178.686636] [<c11ac819>] search_binary_handler+0x89/0x1c0
[ 178.686639] [<c11add40>] do_execveat_common+0x4c0/0x620
[ 178.686653] [<c11673e3>] ? kmemdup+0x33/0x50
[ 178.686659] [<c10c5e3b>] ? __call_rcu.constprop.66+0xbb/0x220
[ 178.686673] [<c11adec4>] do_execve+0x24/0x30
[ 178.686679] [<c107c0be>] ____call_usermodehelper+0xde/0x120
[ 178.686684] [<c1677501>] ret_from_kernel_thread+0x21/0x30
[ 178.686696] [<c107bfe0>] ? __request_module+0x240/0x240
[ 178.686701] ---[ end trace 8b3f5341f50e6c88 ]---
-boris
next prev parent reply other threads:[~2015-07-29 3:02 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-25 5:36 Andy Lutomirski
2015-07-25 5:36 ` [PATCH v4 1/3] x86/ldt: Make modify_ldt synchronous Andy Lutomirski
2015-07-25 9:03 ` Borislav Petkov
2015-07-25 5:36 ` [PATCH v4 2/3] x86/ldt: Make modify_ldt optional Andy Lutomirski
2015-07-25 6:23 ` Willy Tarreau
2015-07-25 6:44 ` Andy Lutomirski
2015-07-25 7:50 ` Willy Tarreau
2015-07-25 13:03 ` [PATCH 4/3] x86/ldt: allow to disable modify_ldt at runtime Willy Tarreau
2015-07-25 16:08 ` Andy Lutomirski
2015-07-25 16:33 ` Willy Tarreau
2015-07-25 17:42 ` Andy Lutomirski
2015-07-25 18:45 ` Willy Tarreau
2015-07-27 19:04 ` Kees Cook
2015-07-27 21:37 ` Willy Tarreau
2015-07-25 9:15 ` [PATCH v4 2/3] x86/ldt: Make modify_ldt optional Borislav Petkov
2015-07-25 16:03 ` Andy Lutomirski
2015-07-25 16:35 ` Willy Tarreau
2015-07-25 5:36 ` [PATCH v4 3/3] selftests/x86, x86/ldt: Add a selftest for modify_ldt Andy Lutomirski
2015-07-27 15:52 ` [PATCH v4.1 3.3] " Andy Lutomirski
2015-07-25 6:27 ` [PATCH v4 0/3] x86: modify_ldt improvement, test, and config option Willy Tarreau
2015-07-27 15:36 ` Boris Ostrovsky
2015-07-27 15:53 ` Andy Lutomirski
2015-07-27 16:18 ` Boris Ostrovsky
2015-07-28 2:20 ` Andy Lutomirski
2015-07-28 3:16 ` Andy Lutomirski
2015-07-28 3:23 ` Andy Lutomirski
2015-07-28 3:43 ` Boris Ostrovsky
2015-07-28 10:29 ` Andrew Cooper
2015-07-28 14:05 ` Boris Ostrovsky
2015-07-28 14:35 ` Andrew Cooper
2015-07-28 14:50 ` Boris Ostrovsky
2015-07-28 15:15 ` Konrad Rzeszutek Wilk
2015-07-28 15:39 ` Boris Ostrovsky
2015-07-28 15:23 ` Andrew Cooper
2015-07-28 15:59 ` [Xen-devel] " Boris Ostrovsky
2015-07-28 15:43 ` Andy Lutomirski
2015-07-28 16:30 ` Andrew Cooper
2015-07-28 17:07 ` Andy Lutomirski
2015-07-28 17:10 ` [Xen-devel] " Boris Ostrovsky
2015-07-29 0:21 ` Andy Lutomirski
2015-07-29 0:47 ` Andrew Cooper
2015-07-29 3:01 ` Boris Ostrovsky [this message]
2015-07-29 4:26 ` Andy Lutomirski
2015-07-29 5:28 ` Andy Lutomirski
2015-07-29 14:21 ` Andrew Cooper
2015-07-29 14:43 ` Boris Ostrovsky
2015-07-29 19:03 ` Andrew Cooper
2015-07-29 21:23 ` Boris Ostrovsky
2015-07-29 21:26 ` Andy Lutomirski
2015-07-29 21:33 ` Boris Ostrovsky
2015-07-29 21:37 ` Andrew Cooper
2015-07-29 22:05 ` Andy Lutomirski
2015-07-29 22:11 ` Andrew Cooper
2015-07-29 22:40 ` Boris Ostrovsky
2015-07-29 22:46 ` David Vrabel
2015-07-29 22:49 ` Boris Ostrovsky
2015-07-29 22:55 ` David Vrabel
2015-07-29 23:02 ` Andrew Cooper
2015-07-29 23:13 ` Andy Lutomirski
2015-07-30 0:29 ` Andrew Cooper
2015-07-30 18:30 ` Andy Lutomirski
2015-07-30 18:54 ` Andrew Cooper
2015-07-30 20:01 ` Boris Ostrovsky
2015-07-30 20:05 ` Andy Lutomirski
2015-07-30 20:18 ` Boris Ostrovsky
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=55B841FF.2000102@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=jbeulich@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sasha.levin@oracle.com \
--cc=security@kernel.org \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xen.org \
/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
Powered by JetHome