From: Vegard Nossum <vegard.nossum@oracle.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: linux-mm@kvack.org, Vlastimil Babka <vbabka@suse.cz>,
Leon Yu <chianglungyu@gmail.com>,
Konstantin Khlebnikov <koct9i@gmail.com>,
Rik van Riel <riel@redhat.com>,
Daniel Forrest <dan.forrest@ssec.wisc.edu>
Subject: Re: [PATCH] mm: correctly handle errors during VMA merging
Date: Tue, 26 Jul 2016 11:24:21 +0200 [thread overview]
Message-ID: <57972C45.5050803@oracle.com> (raw)
In-Reply-To: <20160726085344.GA7370@node.shutemov.name>
On 07/26/2016 10:53 AM, Kirill A. Shutemov wrote:
> On Tue, Jul 26, 2016 at 08:34:03AM +0200, Vegard Nossum wrote:
>> Using trinity + fault injection I've been running into this bug a lot:
>>
>> ==================================================================
>> BUG: KASAN: out-of-bounds in mprotect_fixup+0x523/0x5a0 at addr ffff8800b9e7d740
>> Read of size 8 by task trinity-c3/6338
[...]
>> I can give the reproducer a spin.
>
> Could you post your reproducer? I guess it requires kernel instrumentation
> to make allocation failure more likely.
I'm sorry but company policy prevents me from posting straight-up
reproducers. But as I said I'm happy to rerun it if you have an
alternative patch.
It should be enough to enable fault injection (echo 1 >
/proc/self/make-it-fail) for the process doing the mprotect().
Vegard
--
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:[~2016-07-26 9:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 6:34 [PATCH] mm: correctly handle errors during VMA merging Vegard Nossum
2016-07-26 7:03 ` Vlastimil Babka
2016-07-26 8:53 ` Kirill A. Shutemov
2016-07-26 9:00 ` Vlastimil Babka
2016-07-26 9:24 ` Vegard Nossum [this message]
2016-07-26 10:54 ` Kirill A. Shutemov
2016-07-26 11:48 ` Kirill A. Shutemov
2016-07-26 20:19 ` Vegard Nossum
2016-07-26 20:30 ` Kirill A. Shutemov
2016-07-27 5:40 ` Vegard Nossum
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=57972C45.5050803@oracle.com \
--to=vegard.nossum@oracle.com \
--cc=chianglungyu@gmail.com \
--cc=dan.forrest@ssec.wisc.edu \
--cc=kirill@shutemov.name \
--cc=koct9i@gmail.com \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
--cc=vbabka@suse.cz \
/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).