From: Pat Erley <pat-lkml@erley.org>
To: "Kirill A. Shutemov" <kirill@shutemov.name>,
Sedat Dilek <sedat.dilek@gmail.com>
Cc: Linux-Next <linux-next@vger.kernel.org>,
kirill.shutemov@linux.intel.com, linux-mm <linux-mm@kvack.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: BUG: non-zero nr_pmds on freeing mm: 1
Date: Mon, 09 Feb 2015 11:45:25 -0600 [thread overview]
Message-ID: <54D8F235.7040105@erley.org> (raw)
In-Reply-To: <20150209171320.GB29522@node.dhcp.inet.fi>
On 02/09/2015 11:13 AM, Kirill A. Shutemov wrote:
> On Mon, Feb 09, 2015 at 06:06:11PM +0100, Sedat Dilek wrote:
>> On Mon, Feb 9, 2015 at 5:42 PM, Kirill A. Shutemov <kirill@shutemov.name> wrote:
>>> On Sat, Feb 07, 2015 at 08:33:02AM +0100, Sedat Dilek wrote:
>>>> On Sat, Feb 7, 2015 at 6:12 AM, Pat Erley <pat-lkml@erley.org> wrote:
>>>>> I'm seeing the message in $subject on my Xen DOM0 on next-20150204 on
>>>>> x86_64. I haven't had time to bisect it, but have seen some discussion on
>>>>> similar topics here recently. I can trigger this pretty reliably by
>>>>> watching Netflix. At some point (minutes to hours) into it, the netflix
>>>>> video goes black (audio keeps going, so it still thinks it's working) and
>>>>> the error appears in dmesg. Refreshing the page gets the video going again,
>>>>> and it will continue playing for some indeterminate amount of time.
>>>>>
>>>>> Kirill, I've CC'd you as looking in the logs, you've patched a false
>>>>> positive trigger of this very recently(patch in kernel I'm running). Am I
>>>>> actually hitting a problem, or is this another false positive case? Any
>>>>> additional details that might help?
>>>>>
>>>>> Dmesg from system attached.
>>>>
>>>> [ CC some mm folks ]
>>>>
>>>> I have seen this, too.
>>>>
>>>> root# grep "BUG: non-zero nr_pmds on freeing mm:" /var/log/kern.log | wc -l
>>>> 21
>>>>
>>>> Checking my logs: On next-20150203 and next-20150204.
>>>>
>>>> I am here not in a VM environment and cannot say what causes these messages.
>>>
>>> Sorry, my fault.
>>>
>>> The patch below should fix that.
>>>
>>> From 11bce596e653302e41f819435912f01ca8cbc27e Mon Sep 17 00:00:00 2001
>>> From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
>>> Date: Mon, 9 Feb 2015 18:34:56 +0200
>>> Subject: [PATCH] mm: fix race on pmd accounting
>>>
>>> Do not account the pmd table to the process if other thread allocated it
>>> under us.
>>>
>>> Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
>>> Reported-by: Sedat Dilek <sedat.dilek@gmail.com>
>>
>> Still building with the fix...
>>
>> Please feel free to add Pat as a reporter.
>>
>> Reported-by: Pat Erley <pat-lkml@erley.org>
>>
>> Is that fixing...?
>>
>> commit daa1b0f29cdccae269123e7f8ae0348dbafdc3a7
>> "mm: account pmd page tables to the process"
>>
>> If yes, please add a Fixes-tag [2]...
>>
>> Fixes: daa1b0f29cdc ("mm: account pmd page tables to the process")
>>
>> I will re-test with LTP/mmap and report.
>
> The commit is not in Linus tree, so the sha1-id is goinging to change.
>
I won't be able to test for at least 6 hours (more likely closer to 8 as
I have to get home, boot the machine, apply patch, compile, reboot, and
wait). So not likely I'll be able to get a 'tested-by' on this one
without holding up the whole flow of the patch.
Thanks for the prompt fix Kirill!
--
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:[~2015-02-09 17:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-07 7:33 BUG: non-zero nr_pmds on freeing mm: 1 Sedat Dilek
2015-02-07 8:42 ` Sedat Dilek
2015-02-07 8:56 ` Pat Erley
2015-02-07 9:20 ` Sedat Dilek
2015-02-07 9:30 ` Sedat Dilek
2015-02-07 22:27 ` Pat Erley
2015-02-07 22:33 ` Sedat Dilek
2015-02-08 7:32 ` Pat Erley
2015-02-09 16:42 ` Kirill A. Shutemov
2015-02-09 17:06 ` Sedat Dilek
2015-02-09 17:13 ` Kirill A. Shutemov
2015-02-09 17:45 ` Pat Erley [this message]
2015-02-09 17:50 ` Sedat Dilek
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=54D8F235.7040105@erley.org \
--to=pat-lkml@erley.org \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=sedat.dilek@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).