On Fri, 26 Aug 2005, Blaisorblade wrote:
> This is a followup to my post of last week (Aug 12) about remap_file_pages
> protection support. I've improved and consolidated the patches and updated
> them against 2.6.13-rc6/rc7 (the same patches apply against both versions).
> I'm sending the full
On Fri, 26 Aug 2005, Blaisorblade wrote:
>
> * The first 2 patches modify the PTE encoding macros and start preparing the
> VM for the new situation (i.e. VMA which have variable protections, which are
> called VM_NONUNIFORM. I dropped the early VM_MANYPROTS name).
What a pity: please revert.
On Fri, 2 Sep 2005, Jeff Dike wrote:
> On Wed, Aug 10, 2005 at 09:37:28PM +0200, Blaisorblade wrote:
> > Also look, on the "set_pte" theme, at the attached patch.
>
> + WARN_ON(!pte_young(*pte) || pte_write(*pte) && !pte_dirty(*pte));
>
> This one has been firing on me, and I decided to fi
On Sun, 4 Sep 2005, Blaisorblade wrote:
> On Friday 02 September 2005 23:02, Hugh Dickins wrote:
> > On Fri, 26 Aug 2005, Blaisorblade wrote:
> > > * The first 2 patches modify the PTE encoding macros and start preparing
> > > the VM for the new situation (i.e. VMA whic
On Wed, 13 Nov 2013, Chen Gang wrote:
> Unfortunately, p?d_alloc() and p?d_free() are not pair!! If p?d_alloc()
> succeed, they may be used, so in the next failure, we have to skip them
> to let exit_mmap() or do_munmap() to process it.
>
> According to "Documentation/vm/locking", 'mm->page_table
