Date:   Mon, 19 Aug 2019 18:24:31 +0300
From:   Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To:     sean.j.christopherson@intel.com
Cc:     linux-sgx@vger.kernel.org
Subject: mmap(), #PF handler and EADD interaction
Message-ID: <20190819152431.x5ajhd67cpqag5ue@linux.intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
User-Agent: NeoMutt/20180716
Sender: linux-sgx-owner@vger.kernel.org
Precedence: bulk

I did some backtracking today how the permission flow worked.

With the maximum VM flags defined for a page, what if EADD is done after
mmap()?  E.g. we first do mmap() with RWX and later EADD with lets say
RW.

The first thing that comes to mind is that the #PF handler should caught
this corner case.

Now the code correctly validates when you do either mmap() and
mprotect() after EADD(s) but I think "other way around" is missing.

/Jarkko