From: Mike Kravetz <mike.kravetz@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
Michal Hocko <mhocko@kernel.org>
Cc: bugzilla-daemon@bugzilla.kernel.org, linux-mm@kvack.org,
blurbdust@gmail.com
Subject: Re: [Bug 199037] New: Kernel bug at mm/hugetlb.c:741
Date: Tue, 6 Mar 2018 13:46:11 -0800 [thread overview]
Message-ID: <7ffa77c8-8624-9c69-d1f5-058ef22c460c@oracle.com> (raw)
In-Reply-To: <20180306133135.4dc344e478d98f0e29f47698@linux-foundation.org>
On 03/06/2018 01:31 PM, Andrew Morton wrote:
>
> (switched to email. Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
>
> On Tue, 06 Mar 2018 21:11:50 +0000 bugzilla-daemon@bugzilla.kernel.org wrote:
>
>> https://bugzilla.kernel.org/show_bug.cgi?id=199037
>>
>> Bug ID: 199037
>> Summary: Kernel bug at mm/hugetlb.c:741
>> Product: Memory Management
>> Version: 2.5
>> Kernel Version: 4.16.0-rc3
>> Hardware: All
>> OS: Linux
>> Tree: Mainline
>> Status: NEW
>> Severity: normal
>> Priority: P1
>> Component: Page Allocator
>> Assignee: akpm@linux-foundation.org
>> Reporter: blurbdust@gmail.com
>> Regression: No
>>
>> Created attachment 274595
>> --> https://bugzilla.kernel.org/attachment.cgi?id=274595&action=edit
>> crash.c
>>
>> Hello,
>> I apologize as this is my first time reporting a bug. When I compile and run
>> the attached file it crashes the latest kernel running in QEMU. Call trace
>> here: https://pastebin.com/1mMQvH0E
>>
>> Let me know if you have any questions.
>>
>
> Thanks for the report.
>
> That's VM_BUG_ON(resv_map->adds_in_progress) in resv_map_release().
>
> Do you know if earlier kernel versions are affected?
>
> It looks quite bisectable. Does the crash happen every time the test
> program is run?
I'll take a look. There was a previous bug in this area:
ff8c0c53: mm/hugetlb.c: don't call region_abort if region_chg fails
--
Mike Kravetz
--
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:[~2018-03-06 21:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-199037-27@https.bugzilla.kernel.org/>
2018-03-06 21:31 ` [Bug 199037] New: Kernel bug at mm/hugetlb.c:741 Andrew Morton
2018-03-06 21:46 ` Mike Kravetz [this message]
2018-03-07 0:31 ` Mike Kravetz
2018-03-07 2:49 ` Nic Losby
2018-03-07 4:19 ` Mike Kravetz
2018-03-07 16:39 ` Mike Kravetz
2018-03-07 23:59 ` [PATCH] hugetlbfs: check for pgoff value overflow Mike Kravetz
2018-03-08 0:57 ` Nic Losby
2018-03-08 1:35 ` Yisheng Xie
2018-03-08 4:25 ` Mike Kravetz
2018-03-08 21:03 ` Mike Kravetz
2018-03-08 21:05 ` [PATCH v2] " Mike Kravetz
2018-03-08 22:15 ` Andrew Morton
2018-03-08 23:37 ` Mike Kravetz
2018-03-08 23:53 ` Andrew Morton
2018-03-09 0:27 ` [PATCH v3] " Mike Kravetz
2018-03-09 1:05 ` Andrew Morton
2018-03-16 10:17 ` Michal Hocko
2018-03-16 16:19 ` Mike Kravetz
2018-03-16 16:53 ` Michal Hocko
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=7ffa77c8-8624-9c69-d1f5-058ef22c460c@oracle.com \
--to=mike.kravetz@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=blurbdust@gmail.com \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=kirill@shutemov.name \
--cc=linux-mm@kvack.org \
--cc=mhocko@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;
as well as URLs for NNTP newsgroup(s).