From: Chen Gang <gang.chen@asianux.com>
To: Hugh Dickins <hughd@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm: revert mremap pud_free anti-fix
Date: Wed, 13 Nov 2013 15:15:48 +0800 [thread overview]
Message-ID: <52832724.1090000@asianux.com> (raw)
In-Reply-To: <525D2B15.8060503@asianux.com>
On 10/15/2013 07:46 PM, Chen Gang wrote:
> On 10/15/2013 06:34 PM, Hugh Dickins wrote:
>> > Revert 1ecfd533f4c5 ("mm/mremap.c: call pud_free() after fail calling
>> > pmd_alloc()"). The original code was correct: pud_alloc(), pmd_alloc(),
>> > pte_alloc_map() ensure that the pud, pmd, pt is already allocated, and
>> > seldom do they need to allocate; on failure, upper levels are freed if
>> > appropriate by the subsequent do_munmap(). Whereas 1ecfd533f4c5 did an
>> > unconditional pud_free() of a most-likely still-in-use pud: saved only
>> > by the near-impossiblity of pmd_alloc() failing.
>> >
> What you said above sounds reasonable to me, but better to provide the
> information below:
>
> - pud_free() for pgd_alloc() in "arch/arm/mm/pgd.c".
>
It is correct, it is for 'new_pgd' which not come from 'mm'.
> - pud_free() for init_stub_pte() in "arch/um/kernel/skas/mmu.c".
>
For me, it need improvement, I have sent related patch for it.
> - more details about do_munmap(), (e.g. do it need mm->page_table_lock)
> or more details about the demo "most-likely still-in-use pud ...".
>
According to "Documentation/vm/locking", 'mm->page_table_lock' is for
using vma list, so not need it when its related vmas are detached from
using vma list.
The related work flow:
do_munmap()->
detach_vmas_to_be_unmapped(); /* so not need mm->page_table_lock */
unmap_region() ->
free_pgtables() ->
free_pgd_range() ->
free_pud_range() ->
free_pmd_range() ->
free_pte_range() ->
pmd_clear();
pte_free_tlb();
pud_clear();
pmd_free_tlb();
pgd_clear();
pud_free_tlb();
Thanks.
>
> Hmm... I am not quite sure about the 3 things, and I will/should
> continue analysing/learning about them, but better to get your reply. :-)
--
Chen Gang
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-11-13 7:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 10:34 Hugh Dickins
2013-10-15 11:46 ` Chen Gang
2013-11-13 7:15 ` Chen Gang [this message]
2013-11-13 5:06 ` [PATCH] arch: um: kernel: skas: mmu: remove pmd_free() and pud_free() for failure processing in init_stub_pte() Chen Gang
2013-11-13 9:07 ` Richard Weinberger
2013-11-13 9:14 ` Chen Gang
2013-11-14 5:20 ` Hugh Dickins
2013-11-14 6:48 ` Chen Gang
2013-11-14 7:33 ` Chen Gang
2013-11-14 7:55 ` Richard Weinberger
2013-11-14 8:57 ` Chen Gang
2013-11-15 2:14 ` Chen Gang
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=52832724.1090000@asianux.com \
--to=gang.chen@asianux.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox