Re: [tip:x86/asm] x86/umip: Add emulation code for UMIP instructions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 11/08/2017 06:14 PM, Paolo Bonzini wrote:
On 08/11/2017 18:09, Denys Vlasenko wrote:
On 11/08/2017 05:57 PM, Linus Torvalds wrote:
On Wed, Nov 8, 2017 at 8:53 AM, Denys Vlasenko <dvlasenk@xxxxxxxxxx>
wrote:
We can postpone enabling UMIP by default by a year or so.
By this time, new Wine will be on majority of users' machines.

So you are suggesting we run unnecessarily insecure, only in order to
not do the emulation that we already have the code for and that the
patch implements?

We ran insecure in this way for ~25 years.

Why?

To avoid having to maintain more obscure, rarely executed code.

As a start, you could propose a patch to disable the emulation code
through a sysctl or Kconfig symbol.

This way, the emulation code will still be in the kernel, and still
need to be maintained.

In my opinion, if we do emulate these insns, then adding even more code
to disable that emulation is not worth doing.

I would be surprised if it takes
more time than what you've spent writing emails in this thread.

Yes, I not only f**ing retarded, I'm also lazy. Thanks guys...
--
To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Stable Commits]     [Linux Stable Kernel]     [Linux Kernel]     [Linux USB Devel]     [Linux Video &Media]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]

  Powered by Linux