linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Leon Yu <chianglungyu@gmail.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Konstantin Khlebnikov <koct9i@gmail.com>,
	Rik van Riel <riel@redhat.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] mm: fix anon_vma->degree underflow in anon_vma endless growing prevention
Date: Tue, 3 Mar 2015 22:05:19 +0800	[thread overview]
Message-ID: <CAP06WZxAy=f_CLm9ZnfixV36ziQVQr8CtAoCB7WohT9m6wH8dw@mail.gmail.com> (raw)
In-Reply-To: <20150303133642.GC2409@dhcp22.suse.cz>

On Tue, Mar 3, 2015 at 9:36 PM, Michal Hocko <mhocko@suse.cz> wrote:
> On Tue 03-03-15 20:02:15, Leon Yu wrote:
>> I have constantly stumbled upon "kernel BUG at mm/rmap.c:399!" after upgrading
>> to 3.19 and had no luck with 4.0-rc1 neither.
>>
>> So, after looking into new logic introduced by commit 7a3ef208e662, ("mm:
>> prevent endless growth of anon_vma hierarchy"), I found chances are that
>> unlink_anon_vmas() is called without incrementing dst->anon_vma->degree in
>> anon_vma_clone() due to allocation failure. If dst->anon_vma is not NULL in
>> error path, its degree will be incorrectly decremented in unlink_anon_vmas()
>> and eventually underflow when exiting as a result of another call to
>> unlink_anon_vmas(). That's how "kernel BUG at mm/rmap.c:399!" is triggered
>> for me.
>>
>> This patch fixes the underflow by dropping dst->anon_vma when allocation
>> fails. It's safe to do so regardless of original value of dst->anon_vma
>> because dst->anon_vma doesn't have valid meaning if anon_vma_clone() fails.
>> Besides, callers don't care dst->anon_vma in such case neither.
>>
>> Signed-off-by: Leon Yu <chianglungyu@gmail.com>
>> Fixes: 7a3ef208e662 ("mm: prevent endless growth of anon_vma hierarchy")
>> Cc: stable@vger.kernel.org # v3.19
>
> Reviewed-by: Michal Hocko <mhocko@suse.cz>
>
> I think we can safely remove the following code as well, because it is
> anon_vma_clone which is responsible to do all the cleanups.

Thanks for the input, I'll send v2 with your cleanup.

- Leon

> diff --git a/mm/mmap.c b/mm/mmap.c
> index 943c6ad18b1d..06a6076c92e5 100644
> --- a/mm/mmap.c
> +++ b/mm/mmap.c
> @@ -774,10 +774,8 @@ again:                     remove_next = 1 + (end > next->vm_end);
>
>                         importer->anon_vma = exporter->anon_vma;
>                         error = anon_vma_clone(importer, exporter);
> -                       if (error) {
> -                               importer->anon_vma = NULL;
> +                       if (error)
>                                 return error;
> -                       }
>                 }
>         }

--
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>

  reply	other threads:[~2015-03-03 14:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03 12:02 Leon Yu
2015-03-03 12:36 ` Konstantin Khlebnikov
2015-03-03 13:36 ` Michal Hocko
2015-03-03 14:05   ` Leon Yu [this message]
2015-03-04  5:54   ` David Rientjes
2015-03-03 22:00 ` David Rientjes

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='CAP06WZxAy=f_CLm9ZnfixV36ziQVQr8CtAoCB7WohT9m6wH8dw@mail.gmail.com' \
    --to=chianglungyu@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=koct9i@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.cz \
    --cc=riel@redhat.com \
    --cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox