On Fri, Oct 26, 2012 at 11:57 AM, Rik van Riel wrote:
>
> It looks like do_wp_page also sets the write bit in the pte
> "entry" before passing it to ptep_set_access_flags, making
> that the place where the write bit is set in the pte.
>
> Is this a bug in do_wp_page?
Hmm. Right you are. That's in
On 10/26/2012 02:48 PM, Linus Torvalds wrote:
On Fri, Oct 26, 2012 at 11:46 AM, Rik van Riel wrote:
The function ptep_set_access_flags is only ever used to upgrade
access permissions to a page.
NOTE: It's *not* "access permissions". It's "access flags".
Big difference. This is not about per
On Fri, Oct 26, 2012 at 11:48 AM, Linus Torvalds
wrote:
>
> NOTE: It's *not* "access permissions". It's "access flags".
>
> Big difference. This is not about permissions at all.
Anyway, modulo the misleading commit messages, ACK from on the series.
Linus
--
To unsubscribe from t
On Fri, Oct 26, 2012 at 11:46 AM, Rik van Riel wrote:
>
> The function ptep_set_access_flags is only ever used to upgrade
> access permissions to a page.
NOTE: It's *not* "access permissions". It's "access flags".
Big difference. This is not about permissions at all.
The access flags are the Ac
The function ptep_set_access_flags is only ever used to upgrade
access permissions to a page. That means the only negative side
effect of not flushing remote TLBs is that other CPUs may incur
spurious page faults, if they happen to access the same address,
and still have a PTE with the old permissi
5 matches
Mail list logo
