From: Chintan Pandya <cpandya@codeaurora.org>
To: vbabka@suse.cz, labbott@redhat.com, catalin.marinas@arm.com,
hannes@cmpxchg.org, f.fainelli@gmail.com, xieyisheng1@huawei.com,
ard.biesheuvel@linaro.org, richard.weiyang@gmail.com,
byungchul.park@lge.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Chintan Pandya <cpandya@codeaurora.org>
Subject: [PATCH 0/2] vunmap and debug objects
Date: Fri, 13 Apr 2018 17:03:52 +0530 [thread overview]
Message-ID: <1523619234-17635-1-git-send-email-cpandya@codeaurora.org> (raw)
I'm not entirely sure, how debug objects are really
useful in vmalloc framework.
I'm assuming they are useful in some ways. So, there
are 2 issues in that. First patch is avoiding possible
race scenario and second patch passes _proper_ args
in debug object APIs. Both these patches can help
debug objects to be in consistent state.
We've observed some list corruptions in debug objects.
However, no claims that these patches will be fixing
them.
If one has an opinion that debug object has no use in
vmalloc framework, I would raise a patch to remove
them from the vunmap leg.
Chintan Pandya (2):
mm: vmalloc: Avoid racy handling of debugobjects in vunmap
mm: vmalloc: Pass proper vm_start into debugobjects
mm/vmalloc.c | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
--
Qualcomm India Private Limited, on behalf of Qualcomm Innovation
Center, Inc., is a member of Code Aurora Forum, a Linux Foundation
Collaborative Project
next reply other threads:[~2018-04-13 11:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 11:33 Chintan Pandya [this message]
2018-04-13 11:33 ` [PATCH 1/2] mm: vmalloc: Avoid racy handling of debugobjects in vunmap Chintan Pandya
2018-04-13 11:33 ` [PATCH 2/2] mm: vmalloc: Pass proper vm_start into debugobjects Chintan Pandya
2018-04-13 12:01 ` Anshuman Khandual
2018-04-16 12:09 ` Chintan Pandya
2018-04-17 3:09 ` Anshuman Khandual
2018-04-17 5:10 ` Chintan Pandya
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=1523619234-17635-1-git-send-email-cpandya@codeaurora.org \
--to=cpandya@codeaurora.org \
--cc=ard.biesheuvel@linaro.org \
--cc=byungchul.park@lge.com \
--cc=catalin.marinas@arm.com \
--cc=f.fainelli@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=richard.weiyang@gmail.com \
--cc=vbabka@suse.cz \
--cc=xieyisheng1@huawei.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 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.