All of lore.kernel.org
 help / color / mirror / Atom feed
From: "long.wanglong" <long.wanglong@huawei.com>
To: Xishi Qiu <qiuxishi@huawei.com>, ryabinin.a.a@gmail.com
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Andrey Konovalov <adech.fo@gmail.com>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Michal Marek <mmarek@suse.cz>,
	zhongjiang@huawei.com, Linux MM <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Wang Long <long.wanglong@huawei.com>
Subject: Re: [PATCH V2] kasan: fix last shadow judgement in memory_is_poisoned_16()
Date: Wed, 9 Sep 2015 14:40:42 +0800	[thread overview]
Message-ID: <55EFD46A.20309@huawei.com> (raw)
In-Reply-To: <55EED09E.3010107@huawei.com>

On 2015/9/8 20:12, Xishi Qiu wrote:
> The shadow which correspond 16 bytes memory may span 2 or 3 bytes. If the
> memory is aligned on 8, then the shadow takes only 2 bytes. So we check
> "shadow_first_bytes" is enough, and need not to call "memory_is_poisoned_1(addr + 15);".
> But the code "if (likely(!last_byte))" is wrong judgement.
> 
> e.g. addr=0, so last_byte = 15 & KASAN_SHADOW_MASK = 7, then the code will
> continue to call "memory_is_poisoned_1(addr + 15);"
> 
> Signed-off-by: Xishi Qiu <qiuxishi@huawei.com>
> ---
>  mm/kasan/kasan.c |    3 +--
>  1 files changed, 1 insertions(+), 2 deletions(-)
> 
> diff --git a/mm/kasan/kasan.c b/mm/kasan/kasan.c
> index 7b28e9c..8da2114 100644
> --- a/mm/kasan/kasan.c
> +++ b/mm/kasan/kasan.c
> @@ -135,12 +135,11 @@ static __always_inline bool memory_is_poisoned_16(unsigned long addr)
>  
>  	if (unlikely(*shadow_addr)) {
>  		u16 shadow_first_bytes = *(u16 *)shadow_addr;
> -		s8 last_byte = (addr + 15) & KASAN_SHADOW_MASK;
>  
>  		if (unlikely(shadow_first_bytes))
>  			return true;
>  
> -		if (likely(!last_byte))
> +		if (likely(IS_ALIGNED(addr, 8)))
>  			return false;
>  
>  		return memory_is_poisoned_1(addr + 15);
> 

Hi,
I also notice this problem, how about another method to fix it:

diff --git a/mm/kasan/kasan.c b/mm/kasan/kasan.c
index 5d65d06..6a20dda 100644
--- a/mm/kasan/kasan.c
+++ b/mm/kasan/kasan.c
@@ -140,7 +140,7 @@ static __always_inline bool memory_is_poisoned_16(unsigned long addr)
                if (unlikely(shadow_first_bytes))
                        return true;

-               if (likely(!last_byte))
+               if (likely(last_byte >= 7))
                        return false;

                return memory_is_poisoned_1(addr + 15);

This method can ensure consistency of code, for example, in memory_is_poisoned_8:

static __always_inline bool memory_is_poisoned_8(unsigned long addr)
{
        u16 *shadow_addr = (u16 *)kasan_mem_to_shadow((void *)addr);

        if (unlikely(*shadow_addr)) {
                if (memory_is_poisoned_1(addr + 7))
                        return true;

                if (likely(((addr + 7) & KASAN_SHADOW_MASK) >= 7))
                        return false;

                return unlikely(*(u8 *)shadow_addr);
        }

        return false;
}

Otherwise, we also should use IS_ALIGNED macro in memory_is_poisoned_8!


Best Regards
Wang Long




--
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>

WARNING: multiple messages have this Message-ID (diff)
From: "long.wanglong" <long.wanglong@huawei.com>
To: Xishi Qiu <qiuxishi@huawei.com>, <ryabinin.a.a@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Andrey Konovalov <adech.fo@gmail.com>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Michal Marek <mmarek@suse.cz>, <zhongjiang@huawei.com>,
	Linux MM <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Wang Long <long.wanglong@huawei.com>
Subject: Re: [PATCH V2] kasan: fix last shadow judgement in memory_is_poisoned_16()
Date: Wed, 9 Sep 2015 14:40:42 +0800	[thread overview]
Message-ID: <55EFD46A.20309@huawei.com> (raw)
In-Reply-To: <55EED09E.3010107@huawei.com>

On 2015/9/8 20:12, Xishi Qiu wrote:
> The shadow which correspond 16 bytes memory may span 2 or 3 bytes. If the
> memory is aligned on 8, then the shadow takes only 2 bytes. So we check
> "shadow_first_bytes" is enough, and need not to call "memory_is_poisoned_1(addr + 15);".
> But the code "if (likely(!last_byte))" is wrong judgement.
> 
> e.g. addr=0, so last_byte = 15 & KASAN_SHADOW_MASK = 7, then the code will
> continue to call "memory_is_poisoned_1(addr + 15);"
> 
> Signed-off-by: Xishi Qiu <qiuxishi@huawei.com>
> ---
>  mm/kasan/kasan.c |    3 +--
>  1 files changed, 1 insertions(+), 2 deletions(-)
> 
> diff --git a/mm/kasan/kasan.c b/mm/kasan/kasan.c
> index 7b28e9c..8da2114 100644
> --- a/mm/kasan/kasan.c
> +++ b/mm/kasan/kasan.c
> @@ -135,12 +135,11 @@ static __always_inline bool memory_is_poisoned_16(unsigned long addr)
>  
>  	if (unlikely(*shadow_addr)) {
>  		u16 shadow_first_bytes = *(u16 *)shadow_addr;
> -		s8 last_byte = (addr + 15) & KASAN_SHADOW_MASK;
>  
>  		if (unlikely(shadow_first_bytes))
>  			return true;
>  
> -		if (likely(!last_byte))
> +		if (likely(IS_ALIGNED(addr, 8)))
>  			return false;
>  
>  		return memory_is_poisoned_1(addr + 15);
> 

Hi,
I also notice this problem, how about another method to fix it:

diff --git a/mm/kasan/kasan.c b/mm/kasan/kasan.c
index 5d65d06..6a20dda 100644
--- a/mm/kasan/kasan.c
+++ b/mm/kasan/kasan.c
@@ -140,7 +140,7 @@ static __always_inline bool memory_is_poisoned_16(unsigned long addr)
                if (unlikely(shadow_first_bytes))
                        return true;

-               if (likely(!last_byte))
+               if (likely(last_byte >= 7))
                        return false;

                return memory_is_poisoned_1(addr + 15);

This method can ensure consistency of code, for example, in memory_is_poisoned_8:

static __always_inline bool memory_is_poisoned_8(unsigned long addr)
{
        u16 *shadow_addr = (u16 *)kasan_mem_to_shadow((void *)addr);

        if (unlikely(*shadow_addr)) {
                if (memory_is_poisoned_1(addr + 7))
                        return true;

                if (likely(((addr + 7) & KASAN_SHADOW_MASK) >= 7))
                        return false;

                return unlikely(*(u8 *)shadow_addr);
        }

        return false;
}

Otherwise, we also should use IS_ALIGNED macro in memory_is_poisoned_8!


Best Regards
Wang Long





  reply	other threads:[~2015-09-09  7:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-08 12:12 [PATCH V2] kasan: fix last shadow judgement in memory_is_poisoned_16() Xishi Qiu
2015-09-08 12:12 ` Xishi Qiu
2015-09-09  6:40 ` long.wanglong [this message]
2015-09-09  6:40   ` long.wanglong
2015-09-09  7:43   ` Xishi Qiu
2015-09-09  7:43     ` Xishi Qiu
2015-09-09  8:10     ` long.wanglong
2015-09-09  8:10       ` long.wanglong
2015-09-09  8:30   ` Andrey Ryabinin
2015-09-09  8:30     ` Andrey Ryabinin
2015-09-09 10:01 ` Andrey Ryabinin
2015-09-09 10:01   ` Andrey Ryabinin

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=55EFD46A.20309@huawei.com \
    --to=long.wanglong@huawei.com \
    --cc=adech.fo@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mmarek@suse.cz \
    --cc=qiuxishi@huawei.com \
    --cc=rusty@rustcorp.com.au \
    --cc=ryabinin.a.a@gmail.com \
    --cc=zhongjiang@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.