Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932626AbbGJOSh (ORCPT ); Fri, 10 Jul 2015 10:18:37 -0400 Received: from out02.mta.xmission.com ([166.70.13.232]:52130 "EHLO out02.mta.xmission.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932407AbbGJOS3 (ORCPT ); Fri, 10 Jul 2015 10:18:29 -0400 From: ebiederm@xmission.com (Eric W. Biederman) To: Andy Lutomirski Cc: Linus Torvalds , Arjan van de Ven , Andy Lutomirski , "the arch\/x86 maintainers" , Linux Kernel Mailing List , Oleg Nesterov , Kees Cook , Peter Zijlstra , Borislav Petkov References: <23d4709cee2fe92c32d41b99c7a3c1823725925a.1436312944.git.luto@kernel.org> <559C8BFE.6050604@linux.intel.com> Date: Fri, 10 Jul 2015 09:12:51 -0500 In-Reply-To: (Andy Lutomirski's message of "Wed, 8 Jul 2015 10:30:27 -0700") Message-ID: <87twtc14po.fsf@x220.int.ebiederm.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-XM-AID: U2FsdGVkX194Tj6/Mb+k7BLYCoRbhqVSiLLyO8PQVrM= X-SA-Exim-Connect-IP: 67.3.205.90 X-SA-Exim-Mail-From: ebiederm@xmission.com X-Spam-Report: * -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP * 0.0 TVD_RCVD_IP Message was received from an IP address * 0.0 T_TM2_M_HEADER_IN_MSG BODY: No description available. * 0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% * [score: 0.5000] * -0.0 DCC_CHECK_NEGATIVE Not listed in DCC * [sa07 1397; Body=1 Fuz1=1 Fuz2=1] * 0.0 T_TooManySym_01 4+ unique symbols in subject * 1.0 T_XMDrugObfuBody_08 obfuscated drug references X-Spam-DCC: XMission; sa07 1397; Body=1 Fuz1=1 Fuz2=1 X-Spam-Combo: ;Andy Lutomirski X-Spam-Relay-Country: X-Spam-Timing: total 336 ms - load_scoreonly_sql: 0.15 (0.0%), signal_user_changed: 4.7 (1.4%), b_tie_ro: 3.1 (0.9%), parse: 1.11 (0.3%), extract_message_metadata: 20 (5.8%), get_uri_detail_list: 1.92 (0.6%), tests_pri_-1000: 10 (2.9%), tests_pri_-950: 1.42 (0.4%), tests_pri_-900: 1.22 (0.4%), tests_pri_-400: 24 (7.0%), check_bayes: 22 (6.6%), b_tokenize: 7 (2.1%), b_tok_get_all: 8 (2.2%), b_comp_prob: 2.4 (0.7%), b_tok_touch_all: 3.0 (0.9%), b_finish: 0.65 (0.2%), tests_pri_0: 263 (78.2%), tests_pri_500: 8 (2.4%), rewrite_mail: 0.00 (0.0%) Subject: Re: [PATCH] x86/kconfig/32: Mark CONFIG_VM86 as BROKEN X-Spam-Flag: No X-SA-Exim-Version: 4.2.1 (built Wed, 24 Sep 2014 11:00:52 -0600) X-SA-Exim-Scanned: Yes (on in02.mta.xmission.com) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2405 Lines: 56 Andy Lutomirski writes: > On Wed, Jul 8, 2015 at 9:59 AM, Linus Torvalds > wrote: >> On Tue, Jul 7, 2015 at 7:33 PM, Arjan van de Ven wrote: >>> >>> if this patch would not be acceptable, at minimum we need some sort of "off >>> by default >>> unless the sysadmin flips a sysfs thing", which is really just a huge hack. >> >> The only thing that matters is whether people use this or not. >> > > I think that the world contains precisely two programs that use the > vm86 syscalls. One is dosemu, and one is a test case I wrote. Wine used to also call vm86. > As far as I can tell (and I'll try to test this better for real later > this week), dosemu already knows how to emulate real mode if vm86 is > unavailable. So it's unclear that turning off the vm86 syscalls > actually breaks anything whatsoever. Yes. This happened after 64bit kernels became common years ago, as the lack of vm86 on 64bit nearly killed the dosemu project. > On the other hand, sys_vm86 fails if the syscall slow path is in use. > That means that quite a few Fedora versions (auditing), anything with > ptrace, seccomp (before 3.16 IIRC), and anything with context tracking > is probably actually *improved* by turning off the vm86 syscalls even > for dosemu users. Is there any chance that vm86 is sufficiently badly broken before this that we can conclude vm86 is not in use? It would really simplify this discussion if we could point to code rot and say that it is clear that no one has been testing this code path for ages, and that the code can't possibly work the way it is now. That would just let us remove vm86. > It only says "[OK]" because my test case isn't careful enough. That's > a failure. I suspect it was a much worse failure a couple versions > ago before my ENOSYS-reworking patch went in. > > I'll try to confirm later this week that dosemu can really handle real > mode without sys_vm86. I have not looked in ages but certainly on 64bit dosemu can. As someone else pointed out dosemu maps the zero page so that may also be a point where vm86 support gets broken. Eric -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/