From: Chris Clayton <chris2553@googlemail.com>
To: Konstantin Khlebnikov <koct9i@gmail.com>,
Oded Gabbay <oded.gabbay@amd.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Daniel Forrest <dan.forrest@ssec.wisc.edu>,
Michal Hocko <mhocko@suse.cz>, Rik van Riel <riel@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
"Elifaz, Dana" <Dana.Elifaz@amd.com>,
"Bridgman, John" <John.Bridgman@amd.com>
Subject: Re: BUG in 3.19.0-rc3+
Date: Sun, 11 Jan 2015 10:57:36 +0000 [thread overview]
Message-ID: <54B25720.2000806@googlemail.com> (raw)
In-Reply-To: <CALYGNiOpw75TJhXX5czdkEsver0HVf+oGX3d8qVKNPRNLygUpQ@mail.gmail.com>
Thanks Konstantin.
[snip]
>>>
>>> Looks like degree (%edx) is 1 on anon-vma desruction.
>>> Probably I've overlooked some weird conrner case in vma splitting/merging.
>>>
>>> Could you try this patch. It disables vma merging end eliminates half
>>> of complicated paths.
>>> As I see merging is optional, everything should work fine without it.
>>>
>>> --- a/mm/mmap.c
>>> +++ b/mm/mmap.c
>>> @@ -1048,7 +1048,7 @@ struct vm_area_struct *vma_merge(struct mm_struct *mm,
>>> * We later require that vma->vm_flags == vm_flags,
>>> * so this tests vma->vm_flags & VM_SPECIAL, too.
>>> */
>>> - if (vm_flags & VM_SPECIAL)
>>> + if (1)
>>> return NULL;
>>>
>>> if (prev)
>>>
>>>
>>>
>>>
>>> Code from your oops.
>>>
>>> Code: 00 ad de 48 89 43 18 e8 c5 f9 00 00 48 8b 45 10 48 8d 55 10 48
>>> 83 e8 10 49 39 d6 74 54 48 8b 7d 08 48 89 eb 8b 57 34 85 d2 74 9e <0f>
>>> 0b 0f 1f 40 00 e8 6b fc ff ff eb 9a 66 0f 1f 84 00 00 00 00
>>> All code
>>> ========
>>> 0: 00 ad de 48 89 43 add %ch,0x438948de(%rbp)
>>> 6: 18 e8 sbb %ch,%al
>>> 8: c5 f9 00 (bad)
>>> b: 00 48 8b add %cl,-0x75(%rax)
>>> e: 45 10 48 8d adc %r9b,-0x73(%r8)
>>> 12: 55 push %rbp
>>> 13: 10 48 83 adc %cl,-0x7d(%rax)
>>> 16: e8 10 49 39 d6 callq 0xffffffffd639492b
>>> 1b: 74 54 je 0x71
>>> 1d: 48 8b 7d 08 mov 0x8(%rbp),%rdi
>>> 21: 48 89 eb mov %rbp,%rbx
>>> 24: 8b 57 34 mov 0x34(%rdi),%edx
>>> 27: 85 d2 test %edx,%edx
>>> 29: 74 9e je 0xffffffffffffffc9
>>> 2b:* 0f 0b ud2 <-- trapping instruction
>>> 2d: 0f 1f 40 00 nopl 0x0(%rax)
>>> 31: e8 6b fc ff ff callq 0xfffffffffffffca1
>>> 36: eb 9a jmp 0xffffffffffffffd2
>>> 38: 66 data16
>>> 39: 0f .byte 0xf
>>> 3a: 1f (bad)
>>> 3b: 84 00 test %al,(%rax)
>>> 3d: 00 00 add %al,(%rax)
>>> ...
>>>
>>> Code starting with the faulting instruction
>>> ===========================================
>>> 0: 0f 0b ud2
>>> 2: 0f 1f 40 00 nopl 0x0(%rax)
>>> 6: e8 6b fc ff ff callq 0xfffffffffffffc76
>>> b: eb 9a jmp 0xffffffffffffffa7
>>> d: 66 data16
>>> e: 0f .byte 0xf
>>> f: 1f (bad)
>>> 10: 84 00 test %al,(%rax)
>>> 12: 00 00 add %al,(%rax)
>>>
>>>
>>> +Added Oded Gabbay <oded.gabbay@amd.com> into cc, he's reported this
>>> problem too.
>>>
>> Thanks for the fast reply.
>>
>> I applied the patch and tested it. I wasn't able to reproduce *my* problem,
>> so you are definitely in the right direction :)
>
> Ok. I've found something. Try patch from attachment.
>
Your patch has fixed the BUG for me. Thank you.
Tested-by: Chris Clayton <chris2553@googlemail.com>
>>
>> Oded
>>
>>>>
>>>> In case it helps, I've attached the xz-compressed related config file.
>>>>
>>>> Chris
>>>>
>>>>>
>>>>> I've attached the full kernel log file for that boot.
>>>>>
>>>>> Chris
>>>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>> Please read the FAQ at http://www.tux.org/lkml/
>>>
next prev parent reply other threads:[~2015-01-11 10:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-10 20:17 BUG in 3.19.0-rc3+ Chris Clayton
2015-01-11 8:16 ` Chris Clayton
2015-01-11 9:37 ` Konstantin Khlebnikov
2015-01-11 9:52 ` Oded Gabbay
2015-01-11 10:21 ` Chris Clayton
2015-01-11 10:28 ` Konstantin Khlebnikov
2015-01-11 10:57 ` Chris Clayton [this message]
2015-01-11 11:33 ` Oded Gabbay
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=54B25720.2000806@googlemail.com \
--to=chris2553@googlemail.com \
--cc=Dana.Elifaz@amd.com \
--cc=John.Bridgman@amd.com \
--cc=akpm@linux-foundation.org \
--cc=dan.forrest@ssec.wisc.edu \
--cc=koct9i@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=oded.gabbay@amd.com \
--cc=riel@redhat.com \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.