From: zijun_hu <zijun_hu@zoho.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: zijun_hu@htc.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] lib/ioremap.c: avoid endless loop under ioremapping improper ranges
Date: Wed, 21 Sep 2016 13:04:26 +0800 [thread overview]
Message-ID: <57E214DA.4020304@zoho.com> (raw)
In-Reply-To: <57E0CE04.2070605@zoho.com>
On 09/20/2016 01:49 PM, zijun_hu wrote:
> From: zijun_hu <zijun_hu@htc.com>
>
> for ioremap_page_range(), endless loop maybe happen if either of parameter
> addr and end is not page aligned, in order to fix this issue and hint range
> parameter requirements BUG_ON() checkup are performed firstly
>
> for ioremap_pte_range(), loop end condition is optimized due to lack of
> relevant macro pte_addr_end()
>
> Signed-off-by: zijun_hu <zijun_hu@htc.com>
> ---
> lib/ioremap.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/lib/ioremap.c b/lib/ioremap.c
> index 86c8911..0058cc8 100644
> --- a/lib/ioremap.c
> +++ b/lib/ioremap.c
> @@ -64,7 +64,7 @@ static int ioremap_pte_range(pmd_t *pmd, unsigned long addr,
> BUG_ON(!pte_none(*pte));
> set_pte_at(&init_mm, addr, pte, pfn_pte(pfn, prot));
> pfn++;
> - } while (pte++, addr += PAGE_SIZE, addr != end);
> + } while (pte++, addr += PAGE_SIZE, addr < end);
> return 0;
> }
>
> @@ -129,6 +129,7 @@ int ioremap_page_range(unsigned long addr,
> int err;
>
> BUG_ON(addr >= end);
> + BUG_ON(!PAGE_ALIGNED(addr | end));
>
> start = addr;
> phys_addr -= addr;
>
another approach is provided in another mail thread as below
i don't known which is more appropriate
From: zijun_hu <zijun_hu@htc.com>
Subject: [PATCH 1/1] lib/ioremap.c: avoid endless loop under ioremapping page
unaligned ranges
endless loop maybe happen if either of parameter addr and end is not
page aligned for kernel API function ioremap_page_range()
in order to fix this issue and alert improper range parameters to user
WARN_ON() checkup and rounding down range lower boundary are performed
firstly, loop end condition within ioremap_pte_range() is optimized due
to lack of relevant macro pte_addr_end()
Signed-off-by: zijun_hu <zijun_hu@htc.com>
---
lib/ioremap.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/lib/ioremap.c b/lib/ioremap.c
index 86c8911..911bdca 100644
--- a/lib/ioremap.c
+++ b/lib/ioremap.c
@@ -64,7 +64,7 @@ static int ioremap_pte_range(pmd_t *pmd, unsigned long addr,
BUG_ON(!pte_none(*pte));
set_pte_at(&init_mm, addr, pte, pfn_pte(pfn, prot));
pfn++;
- } while (pte++, addr += PAGE_SIZE, addr != end);
+ } while (pte++, addr += PAGE_SIZE, addr < end && addr >= PAGE_SIZE);
return 0;
}
@@ -129,7 +129,9 @@ int ioremap_page_range(unsigned long addr,
int err;
BUG_ON(addr >= end);
+ WARN_ON(!PAGE_ALIGNED(addr) || !PAGE_ALIGNED(end));
+ addr = round_down(addr, PAGE_SIZE);
start = addr;
phys_addr -= addr;
pgd = pgd_offset_k(addr);
--
1.9.1
--
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>
prev parent reply other threads:[~2016-09-21 5:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 5:49 zijun_hu
2016-09-21 5:04 ` zijun_hu [this message]
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=57E214DA.4020304@zoho.com \
--to=zijun_hu@zoho.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=zijun_hu@htc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox