From: chengang@emindsoft.com.cn
To: akpm@linux-foundation.org, aryabinin@virtuozzo.com,
glider@google.com, dvyukov@google.com
Cc: kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Chen Gang <chengang@emindsoft.com.cn>,
Chen Gang <gang.chen.5i5j@gmail.com>
Subject: [PATCH] mm/kasan/kasan.h: Fix boolean checking issue for kasan_report_enabled()
Date: Mon, 2 May 2016 13:36:14 +0800 [thread overview]
Message-ID: <1462167374-6321-1-git-send-email-chengang@emindsoft.com.cn> (raw)
From: Chen Gang <chengang@emindsoft.com.cn>
According to kasan_[dis|en]able_current() comments and the kasan_depth'
s initialization, if kasan_depth is zero, it means disable.
So need use "!!kasan_depth" instead of "!kasan_depth" for checking
enable.
Signed-off-by: Chen Gang <gang.chen.5i5j@gmail.com>
---
mm/kasan/kasan.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/kasan/kasan.h b/mm/kasan/kasan.h
index 7da78a6..6464b8f 100644
--- a/mm/kasan/kasan.h
+++ b/mm/kasan/kasan.h
@@ -102,7 +102,7 @@ static inline const void *kasan_shadow_to_mem(const void *shadow_addr)
static inline bool kasan_report_enabled(void)
{
- return !current->kasan_depth;
+ return !!current->kasan_depth;
}
void kasan_report(unsigned long addr, size_t size,
--
1.9.3
--
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 reply other threads:[~2016-05-02 5:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 5:36 chengang [this message]
2016-05-02 8:26 ` Dmitry Vyukov
2016-05-02 11:11 ` Chen Gang
2016-05-02 11:21 ` Dmitry Vyukov
2016-05-02 12:27 ` Chen Gang
2016-05-02 12:42 ` Alexander Potapenko
2016-05-02 13:51 ` Chen Gang
2016-05-02 14:23 ` Alexander Potapenko
2016-05-02 15:13 ` Chen Gang
2016-05-02 15:35 ` Alexander Potapenko
2016-05-02 16:23 ` Chen Gang
2016-05-02 16:38 ` Chen Gang
2016-05-14 3:30 ` Chen Gang
2016-05-14 10:34 ` Alexander Potapenko
2016-05-02 11:34 ` Alexander Potapenko
2016-05-02 12:09 ` Chen Gang
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=1462167374-6321-1-git-send-email-chengang@emindsoft.com.cn \
--to=chengang@emindsoft.com.cn \
--cc=akpm@linux-foundation.org \
--cc=aryabinin@virtuozzo.com \
--cc=dvyukov@google.com \
--cc=gang.chen.5i5j@gmail.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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