From: Greg KH <gregkh@linuxfoundation.org>
To: Gregory Panic <airman.price@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RW GDT replaced by Read-Only GDT and a GPL Interface
Date: Sun, 29 Apr 2018 17:59:24 +0200 [thread overview]
Message-ID: <20180429155924.GA28565@kroah.com> (raw)
In-Reply-To: <CAMB+E4gS=F8kXMNTtKdLr9y-C_+NaSPQm3M1m9xC0Sbhn+hjYw@mail.gmail.com>
On Tue, Apr 17, 2018 at 05:33:25PM -0400, Gregory Panic wrote:
> Hi,
>
> I have been working on a VMX driver for a custom hypervisor which
> depends on features that KVM is not built for. Up until recently
> (4.12.x), our module has been working just fine. When we started to
> build support for Ubuntu 18.04 (4.15.x+), we ran into an issue.
>
> Unfortunately the following commits broke functionality, causing
> kernel segfaults, due to a placing the GDT in the FIXMAP area, and
> setting that mapping to Read-Only.
> #69218e47994da614e7af600bf06887750ab6657a
> and
> #45fc8757d1d2128e342b4e7ef39adedf7752faac
>
> Up until now, the GDT has been Read-Write, which allowed for resetting
> the TSS to available, and then Reloading it after a VMExit. The KVM
> and Xen work-arounds for this were implemented by creating a GPL'd
> interface to remap the GDT to the original Read/Write mapping and then
> back.
>
> Up to this point we've been able to maintain independence from GPL,
As has been stated numberous times, the lack of EXPORT_SYMBOL_GPL() does
NOT mean that the interface you are using is not covered under the GPL
license of the kernel.
Please consult with an IP lawyer for the details if you are interested.
Best of luck with your driver!
greg k-h
next prev parent reply other threads:[~2018-04-29 15:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 21:33 RW GDT replaced by Read-Only GDT and a GPL Interface Gregory Panic
2018-04-29 15:59 ` Greg KH [this message]
2018-04-30 21:02 ` Gregory Panic
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=20180429155924.GA28565@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=airman.price@gmail.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.