* [PATCH v2] lib: Use PFN_PHYS() in devmem_is_allowed()
@ 2021-07-30 7:43 ` Liang Wang
0 siblings, 0 replies; 12+ messages in thread
From: Liang Wang @ 2021-07-30 7:43 UTC (permalink / raw)
To: palmerdabbelt, mcgrof, linux-kernel, gregkh, linux, linux-arm-kernel
Cc: stable, wangliang101, wangle6, kepler.chenxin, nixiaoming,
wangkefeng.wang
The physical address may exceed 32 bits on ARM(when ARM_LPAE enabled),
use PFN_PHYS() in devmem_is_allowed(), or the physical address may
overflow and be truncated.
This bug was initially introduced from v2.6.37, and the function was moved
to lib when v5.11.
Fixes: 087aaffcdf9c ("ARM: implement CONFIG_STRICT_DEVMEM by disabling access to RAM via /dev/mem")
Fixes: 527701eda5f1 ("lib: Add a generic version of devmem_is_allowed()")
Cc: stable@vger.kernel.org # v2.6.37
Signed-off-by: Liang Wang <wangliang101@huawei.com>
---
v2: update subject and changelog
lib/devmem_is_allowed.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/devmem_is_allowed.c b/lib/devmem_is_allowed.c
index c0d67c541849..60be9e24bd57 100644
--- a/lib/devmem_is_allowed.c
+++ b/lib/devmem_is_allowed.c
@@ -19,7 +19,7 @@
*/
int devmem_is_allowed(unsigned long pfn)
{
- if (iomem_is_exclusive(pfn << PAGE_SHIFT))
+ if (iomem_is_exclusive(PFN_PHYS(pfn)))
return 0;
if (!page_is_ram(pfn))
return 1;
--
2.32.0
^ permalink raw reply related [flat|nested] 12+ messages in thread* [PATCH v2] lib: Use PFN_PHYS() in devmem_is_allowed()
@ 2021-07-30 7:43 ` Liang Wang
0 siblings, 0 replies; 12+ messages in thread
From: Liang Wang @ 2021-07-30 7:43 UTC (permalink / raw)
To: palmerdabbelt, mcgrof, linux-kernel, gregkh, linux, linux-arm-kernel
Cc: stable, wangliang101, wangle6, kepler.chenxin, nixiaoming,
wangkefeng.wang
The physical address may exceed 32 bits on ARM(when ARM_LPAE enabled),
use PFN_PHYS() in devmem_is_allowed(), or the physical address may
overflow and be truncated.
This bug was initially introduced from v2.6.37, and the function was moved
to lib when v5.11.
Fixes: 087aaffcdf9c ("ARM: implement CONFIG_STRICT_DEVMEM by disabling access to RAM via /dev/mem")
Fixes: 527701eda5f1 ("lib: Add a generic version of devmem_is_allowed()")
Cc: stable@vger.kernel.org # v2.6.37
Signed-off-by: Liang Wang <wangliang101@huawei.com>
---
v2: update subject and changelog
lib/devmem_is_allowed.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/devmem_is_allowed.c b/lib/devmem_is_allowed.c
index c0d67c541849..60be9e24bd57 100644
--- a/lib/devmem_is_allowed.c
+++ b/lib/devmem_is_allowed.c
@@ -19,7 +19,7 @@
*/
int devmem_is_allowed(unsigned long pfn)
{
- if (iomem_is_exclusive(pfn << PAGE_SHIFT))
+ if (iomem_is_exclusive(PFN_PHYS(pfn)))
return 0;
if (!page_is_ram(pfn))
return 1;
--
2.32.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply related [flat|nested] 12+ messages in thread* Re: [PATCH v2] lib: Use PFN_PHYS() in devmem_is_allowed()
2021-07-30 7:43 ` Liang Wang
@ 2021-07-30 19:36 ` Luis Chamberlain
-1 siblings, 0 replies; 12+ messages in thread
From: Luis Chamberlain @ 2021-07-30 19:36 UTC (permalink / raw)
To: Liang Wang
Cc: palmerdabbelt, linux-kernel, gregkh, linux, linux-arm-kernel,
stable, wangle6, kepler.chenxin, nixiaoming, wangkefeng.wang
On Fri, Jul 30, 2021 at 03:43:15PM +0800, Liang Wang wrote:
> The physical address may exceed 32 bits on ARM(when ARM_LPAE enabled),
> use PFN_PHYS() in devmem_is_allowed(),
First off, good catch!
This should not be ARM specific, this should just say:
on 32-bit systems with more than 32 bits of physcial address
Also, towards then end then explain that in practice, yes,
this is probably just ARM which is affected. By explaining
this, it ensures folks are aware of the affected systems.
May be good to refer to commit 947d0496cf3e1 ("generic: make PFN_PHYS
explicitly return phys_addr_t") which added the original PFN_PHYS()
casting to phys_addr_t to resolve the same problem.
> or the physical address may overflow and be truncated.
Indeed. How did you find this issue? Can you describe that in the commit
log? Was it a real world issue or did you do just code inspection? Or
was there a bot which helped you?
> This bug was initially introduced from v2.6.37, and the function was moved
> to lib when v5.11.
>
> Fixes: 087aaffcdf9c ("ARM: implement CONFIG_STRICT_DEVMEM by disabling access to RAM via /dev/mem")
> Fixes: 527701eda5f1 ("lib: Add a generic version of devmem_is_allowed()")
> Cc: stable@vger.kernel.org # v2.6.37
> Signed-off-by: Liang Wang <wangliang101@huawei.com>
Other than that:
Reviewed-by: Luis Chamberlain <mcgrof@kernel.org>
Luis
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: [PATCH v2] lib: Use PFN_PHYS() in devmem_is_allowed()
@ 2021-07-30 19:36 ` Luis Chamberlain
0 siblings, 0 replies; 12+ messages in thread
From: Luis Chamberlain @ 2021-07-30 19:36 UTC (permalink / raw)
To: Liang Wang
Cc: palmerdabbelt, linux-kernel, gregkh, linux, linux-arm-kernel,
stable, wangle6, kepler.chenxin, nixiaoming, wangkefeng.wang
On Fri, Jul 30, 2021 at 03:43:15PM +0800, Liang Wang wrote:
> The physical address may exceed 32 bits on ARM(when ARM_LPAE enabled),
> use PFN_PHYS() in devmem_is_allowed(),
First off, good catch!
This should not be ARM specific, this should just say:
on 32-bit systems with more than 32 bits of physcial address
Also, towards then end then explain that in practice, yes,
this is probably just ARM which is affected. By explaining
this, it ensures folks are aware of the affected systems.
May be good to refer to commit 947d0496cf3e1 ("generic: make PFN_PHYS
explicitly return phys_addr_t") which added the original PFN_PHYS()
casting to phys_addr_t to resolve the same problem.
> or the physical address may overflow and be truncated.
Indeed. How did you find this issue? Can you describe that in the commit
log? Was it a real world issue or did you do just code inspection? Or
was there a bot which helped you?
> This bug was initially introduced from v2.6.37, and the function was moved
> to lib when v5.11.
>
> Fixes: 087aaffcdf9c ("ARM: implement CONFIG_STRICT_DEVMEM by disabling access to RAM via /dev/mem")
> Fixes: 527701eda5f1 ("lib: Add a generic version of devmem_is_allowed()")
> Cc: stable@vger.kernel.org # v2.6.37
> Signed-off-by: Liang Wang <wangliang101@huawei.com>
Other than that:
Reviewed-by: Luis Chamberlain <mcgrof@kernel.org>
Luis
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 12+ messages in thread* 答复: [PATCH v2] lib: Use PFN_PHYS() in devmem_is_allowed()
2021-07-30 19:36 ` Luis Chamberlain
@ 2021-07-31 2:04 ` wangliang (C)
-1 siblings, 0 replies; 12+ messages in thread
From: wangliang (C) @ 2021-07-31 2:04 UTC (permalink / raw)
To: Luis Chamberlain
Cc: palmerdabbelt, linux-kernel, gregkh, linux, linux-arm-kernel,
stable, Wangle (RTOS FAE), Chenxin (RTOS),
Nixiaoming, Wangkefeng (OS Kernel Lab)
I'm glad to get the reply.
I found this problem not only with the arm, but also with the x86. Is it good to fixed both in only one patch? I found this problem in actual work. When CONFIG_STRICT_DEVMEM is enabled on the ARM and devmem is used to map a high address that is not in the iomem address range, an unexpected error indicating no permission is returned. Then i find the bug.
-----邮件原件-----
发件人: Luis Chamberlain [mailto:mcgrof@infradead.org] 代表 Luis Chamberlain
发送时间: 2021年7月31日 3:37
收件人: wangliang (C) <wangliang101@huawei.com>
抄送: palmerdabbelt@google.com; linux-kernel@vger.kernel.org; gregkh@linuxfoundation.org; linux@armlinux.org.uk; linux-arm-kernel@lists.infradead.org; stable@vger.kernel.org; Wangle (RTOS FAE) <wangle6@huawei.com>; Chenxin (RTOS) <kepler.chenxin@huawei.com>; Nixiaoming <nixiaoming@huawei.com>; Wangkefeng (OS Kernel Lab) <wangkefeng.wang@huawei.com>
主题: Re: [PATCH v2] lib: Use PFN_PHYS() in devmem_is_allowed()
On Fri, Jul 30, 2021 at 03:43:15PM +0800, Liang Wang wrote:
> The physical address may exceed 32 bits on ARM(when ARM_LPAE enabled),
> use PFN_PHYS() in devmem_is_allowed(),
First off, good catch!
This should not be ARM specific, this should just say:
on 32-bit systems with more than 32 bits of physcial address
Also, towards then end then explain that in practice, yes, this is probably just ARM which is affected. By explaining this, it ensures folks are aware of the affected systems.
May be good to refer to commit 947d0496cf3e1 ("generic: make PFN_PHYS explicitly return phys_addr_t") which added the original PFN_PHYS() casting to phys_addr_t to resolve the same problem.
> or the physical address may overflow and be truncated.
Indeed. How did you find this issue? Can you describe that in the commit log? Was it a real world issue or did you do just code inspection? Or was there a bot which helped you?
> This bug was initially introduced from v2.6.37, and the function was
> moved to lib when v5.11.
>
> Fixes: 087aaffcdf9c ("ARM: implement CONFIG_STRICT_DEVMEM by disabling
> access to RAM via /dev/mem")
> Fixes: 527701eda5f1 ("lib: Add a generic version of
> devmem_is_allowed()")
> Cc: stable@vger.kernel.org # v2.6.37
> Signed-off-by: Liang Wang <wangliang101@huawei.com>
Other than that:
Reviewed-by: Luis Chamberlain <mcgrof@kernel.org>
Luis
^ permalink raw reply [flat|nested] 12+ messages in thread* 答复: [PATCH v2] lib: Use PFN_PHYS() in devmem_is_allowed()
@ 2021-07-31 2:04 ` wangliang (C)
0 siblings, 0 replies; 12+ messages in thread
From: wangliang (C) @ 2021-07-31 2:04 UTC (permalink / raw)
To: Luis Chamberlain
Cc: palmerdabbelt, linux-kernel, gregkh, linux, linux-arm-kernel,
stable, Wangle (RTOS FAE), Chenxin (RTOS),
Nixiaoming, Wangkefeng (OS Kernel Lab)
I'm glad to get the reply.
I found this problem not only with the arm, but also with the x86. Is it good to fixed both in only one patch? I found this problem in actual work. When CONFIG_STRICT_DEVMEM is enabled on the ARM and devmem is used to map a high address that is not in the iomem address range, an unexpected error indicating no permission is returned. Then i find the bug.
-----邮件原件-----
发件人: Luis Chamberlain [mailto:mcgrof@infradead.org] 代表 Luis Chamberlain
发送时间: 2021年7月31日 3:37
收件人: wangliang (C) <wangliang101@huawei.com>
抄送: palmerdabbelt@google.com; linux-kernel@vger.kernel.org; gregkh@linuxfoundation.org; linux@armlinux.org.uk; linux-arm-kernel@lists.infradead.org; stable@vger.kernel.org; Wangle (RTOS FAE) <wangle6@huawei.com>; Chenxin (RTOS) <kepler.chenxin@huawei.com>; Nixiaoming <nixiaoming@huawei.com>; Wangkefeng (OS Kernel Lab) <wangkefeng.wang@huawei.com>
主题: Re: [PATCH v2] lib: Use PFN_PHYS() in devmem_is_allowed()
On Fri, Jul 30, 2021 at 03:43:15PM +0800, Liang Wang wrote:
> The physical address may exceed 32 bits on ARM(when ARM_LPAE enabled),
> use PFN_PHYS() in devmem_is_allowed(),
First off, good catch!
This should not be ARM specific, this should just say:
on 32-bit systems with more than 32 bits of physcial address
Also, towards then end then explain that in practice, yes, this is probably just ARM which is affected. By explaining this, it ensures folks are aware of the affected systems.
May be good to refer to commit 947d0496cf3e1 ("generic: make PFN_PHYS explicitly return phys_addr_t") which added the original PFN_PHYS() casting to phys_addr_t to resolve the same problem.
> or the physical address may overflow and be truncated.
Indeed. How did you find this issue? Can you describe that in the commit log? Was it a real world issue or did you do just code inspection? Or was there a bot which helped you?
> This bug was initially introduced from v2.6.37, and the function was
> moved to lib when v5.11.
>
> Fixes: 087aaffcdf9c ("ARM: implement CONFIG_STRICT_DEVMEM by disabling
> access to RAM via /dev/mem")
> Fixes: 527701eda5f1 ("lib: Add a generic version of
> devmem_is_allowed()")
> Cc: stable@vger.kernel.org # v2.6.37
> Signed-off-by: Liang Wang <wangliang101@huawei.com>
Other than that:
Reviewed-by: Luis Chamberlain <mcgrof@kernel.org>
Luis
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 12+ messages in thread
[parent not found: <20210730064915.56249-1-wangliang101@huawei.com>]
* Re: [PATCH v2] lib: Use PFN_PHYS() in devmem_is_allowed()
[not found] <20210730064915.56249-1-wangliang101@huawei.com>
@ 2021-07-30 7:04 ` Kefeng Wang
0 siblings, 0 replies; 12+ messages in thread
From: Kefeng Wang @ 2021-07-30 7:04 UTC (permalink / raw)
To: Liang Wang, palmerdabbelt, mcgrof, linux-kernel, gregkh, linux,
linux-arm-kernel
Cc: stable, wangle6, kepler.chenxin, nixiaoming
On 2021/7/30 14:49, Liang Wang wrote:
> The physical address may exceed 32 bits on ARM(when ARM_LPAE enabled),
> use PFN_PHYS() in devmem_is_allowed(), or the physical address may
> overflow and be truncated.
>
> This bug was initially introduced from v2.6.37, and the function was moved
> to lib when v5.10.
>
> Fixes: 087aaffcdf9c ("ARM: implement CONFIG_STRICT_DEVMEM by disabling access to RAM via /dev/mem")
> Fixes: 527701eda5f1 ("lib: Add a generic version of devmem_is_allowed()")
> Cc: stable@vger.kernel.org # v2.6.37
> Signed-off-by: Liang Wang <wangliang101@huawei.com>
Reviewed-by: Kefeng Wang <wangkefeng.wang@huawei.com>
> ---
> v2: update subject and changelog
> lib/devmem_is_allowed.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/devmem_is_allowed.c b/lib/devmem_is_allowed.c
> index c0d67c541849..60be9e24bd57 100644
> --- a/lib/devmem_is_allowed.c
> +++ b/lib/devmem_is_allowed.c
> @@ -19,7 +19,7 @@
> */
> int devmem_is_allowed(unsigned long pfn)
> {
> - if (iomem_is_exclusive(pfn << PAGE_SHIFT))
> + if (iomem_is_exclusive(PFN_PHYS(pfn)))
> return 0;
> if (!page_is_ram(pfn))
> return 1;
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: [PATCH v2] lib: Use PFN_PHYS() in devmem_is_allowed()
@ 2021-07-30 7:04 ` Kefeng Wang
0 siblings, 0 replies; 12+ messages in thread
From: Kefeng Wang @ 2021-07-30 7:04 UTC (permalink / raw)
To: Liang Wang, palmerdabbelt, mcgrof, linux-kernel, gregkh, linux,
linux-arm-kernel
Cc: stable, wangle6, kepler.chenxin, nixiaoming
On 2021/7/30 14:49, Liang Wang wrote:
> The physical address may exceed 32 bits on ARM(when ARM_LPAE enabled),
> use PFN_PHYS() in devmem_is_allowed(), or the physical address may
> overflow and be truncated.
>
> This bug was initially introduced from v2.6.37, and the function was moved
> to lib when v5.10.
>
> Fixes: 087aaffcdf9c ("ARM: implement CONFIG_STRICT_DEVMEM by disabling access to RAM via /dev/mem")
> Fixes: 527701eda5f1 ("lib: Add a generic version of devmem_is_allowed()")
> Cc: stable@vger.kernel.org # v2.6.37
> Signed-off-by: Liang Wang <wangliang101@huawei.com>
Reviewed-by: Kefeng Wang <wangkefeng.wang@huawei.com>
> ---
> v2: update subject and changelog
> lib/devmem_is_allowed.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/devmem_is_allowed.c b/lib/devmem_is_allowed.c
> index c0d67c541849..60be9e24bd57 100644
> --- a/lib/devmem_is_allowed.c
> +++ b/lib/devmem_is_allowed.c
> @@ -19,7 +19,7 @@
> */
> int devmem_is_allowed(unsigned long pfn)
> {
> - if (iomem_is_exclusive(pfn << PAGE_SHIFT))
> + if (iomem_is_exclusive(PFN_PHYS(pfn)))
> return 0;
> if (!page_is_ram(pfn))
> return 1;
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: [PATCH v2] lib: Use PFN_PHYS() in devmem_is_allowed()
2021-07-30 7:04 ` Kefeng Wang
@ 2021-08-04 0:20 ` Palmer Dabbelt
-1 siblings, 0 replies; 12+ messages in thread
From: Palmer Dabbelt @ 2021-08-04 0:20 UTC (permalink / raw)
To: wangkefeng.wang
Cc: wangliang101, mcgrof, linux-kernel, Greg KH, linux,
linux-arm-kernel, stable, wangle6, kepler.chenxin, nixiaoming
On Fri, 30 Jul 2021 00:04:05 PDT (-0700), wangkefeng.wang@huawei.com wrote:
>
> On 2021/7/30 14:49, Liang Wang wrote:
>> The physical address may exceed 32 bits on ARM(when ARM_LPAE enabled),
>> use PFN_PHYS() in devmem_is_allowed(), or the physical address may
>> overflow and be truncated.
>>
>> This bug was initially introduced from v2.6.37, and the function was moved
>> to lib when v5.10.
>>
>> Fixes: 087aaffcdf9c ("ARM: implement CONFIG_STRICT_DEVMEM by disabling access to RAM via /dev/mem")
>> Fixes: 527701eda5f1 ("lib: Add a generic version of devmem_is_allowed()")
>> Cc: stable@vger.kernel.org # v2.6.37
>> Signed-off-by: Liang Wang <wangliang101@huawei.com>
> Reviewed-by: Kefeng Wang <wangkefeng.wang@huawei.com>
>> ---
>> v2: update subject and changelog
>> lib/devmem_is_allowed.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/lib/devmem_is_allowed.c b/lib/devmem_is_allowed.c
>> index c0d67c541849..60be9e24bd57 100644
>> --- a/lib/devmem_is_allowed.c
>> +++ b/lib/devmem_is_allowed.c
>> @@ -19,7 +19,7 @@
>> */
>> int devmem_is_allowed(unsigned long pfn)
>> {
>> - if (iomem_is_exclusive(pfn << PAGE_SHIFT))
>> + if (iomem_is_exclusive(PFN_PHYS(pfn)))
>> return 0;
>> if (!page_is_ram(pfn))
>> return 1;
Acked-by: Palmer Dabbelt <palmerdabbelt@google.com>
I only see the reply so I'm assuming this is going in through some other
tree, but LMK if you want it via the RISC-V tree as IIRC we're using it
too.
Thanks!
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: [PATCH v2] lib: Use PFN_PHYS() in devmem_is_allowed()
@ 2021-08-04 0:20 ` Palmer Dabbelt
0 siblings, 0 replies; 12+ messages in thread
From: Palmer Dabbelt @ 2021-08-04 0:20 UTC (permalink / raw)
To: wangkefeng.wang
Cc: wangliang101, mcgrof, linux-kernel, Greg KH, linux,
linux-arm-kernel, stable, wangle6, kepler.chenxin, nixiaoming
On Fri, 30 Jul 2021 00:04:05 PDT (-0700), wangkefeng.wang@huawei.com wrote:
>
> On 2021/7/30 14:49, Liang Wang wrote:
>> The physical address may exceed 32 bits on ARM(when ARM_LPAE enabled),
>> use PFN_PHYS() in devmem_is_allowed(), or the physical address may
>> overflow and be truncated.
>>
>> This bug was initially introduced from v2.6.37, and the function was moved
>> to lib when v5.10.
>>
>> Fixes: 087aaffcdf9c ("ARM: implement CONFIG_STRICT_DEVMEM by disabling access to RAM via /dev/mem")
>> Fixes: 527701eda5f1 ("lib: Add a generic version of devmem_is_allowed()")
>> Cc: stable@vger.kernel.org # v2.6.37
>> Signed-off-by: Liang Wang <wangliang101@huawei.com>
> Reviewed-by: Kefeng Wang <wangkefeng.wang@huawei.com>
>> ---
>> v2: update subject and changelog
>> lib/devmem_is_allowed.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/lib/devmem_is_allowed.c b/lib/devmem_is_allowed.c
>> index c0d67c541849..60be9e24bd57 100644
>> --- a/lib/devmem_is_allowed.c
>> +++ b/lib/devmem_is_allowed.c
>> @@ -19,7 +19,7 @@
>> */
>> int devmem_is_allowed(unsigned long pfn)
>> {
>> - if (iomem_is_exclusive(pfn << PAGE_SHIFT))
>> + if (iomem_is_exclusive(PFN_PHYS(pfn)))
>> return 0;
>> if (!page_is_ram(pfn))
>> return 1;
Acked-by: Palmer Dabbelt <palmerdabbelt@google.com>
I only see the reply so I'm assuming this is going in through some other
tree, but LMK if you want it via the RISC-V tree as IIRC we're using it
too.
Thanks!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: [PATCH v2] lib: Use PFN_PHYS() in devmem_is_allowed()
2021-08-04 0:20 ` Palmer Dabbelt
@ 2021-08-04 5:03 ` Kefeng Wang
-1 siblings, 0 replies; 12+ messages in thread
From: Kefeng Wang @ 2021-08-04 5:03 UTC (permalink / raw)
To: Palmer Dabbelt
Cc: wangliang101, mcgrof, linux-kernel, Greg KH, linux,
linux-arm-kernel, stable, wangle6, kepler.chenxin, nixiaoming
On 2021/8/4 8:20, Palmer Dabbelt wrote:
> On Fri, 30 Jul 2021 00:04:05 PDT (-0700), wangkefeng.wang@huawei.com
> wrote:
>>
>> On 2021/7/30 14:49, Liang Wang wrote:
>>> The physical address may exceed 32 bits on ARM(when ARM_LPAE enabled),
>>> use PFN_PHYS() in devmem_is_allowed(), or the physical address may
>>> overflow and be truncated.
>>>
>>> This bug was initially introduced from v2.6.37, and the function was
>>> moved
>>> to lib when v5.10.
>>>
>>> Fixes: 087aaffcdf9c ("ARM: implement CONFIG_STRICT_DEVMEM by
>>> disabling access to RAM via /dev/mem")
>>> Fixes: 527701eda5f1 ("lib: Add a generic version of
>>> devmem_is_allowed()")
>>> Cc: stable@vger.kernel.org # v2.6.37
>>> Signed-off-by: Liang Wang <wangliang101@huawei.com>
>> Reviewed-by: Kefeng Wang <wangkefeng.wang@huawei.com>
>>> ---
>>> v2: update subject and changelog
>>> lib/devmem_is_allowed.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
...
> Acked-by: Palmer Dabbelt <palmerdabbelt@google.com>
>
> I only see the reply so I'm assuming this is going in through some
> other tree, but LMK if you want it via the RISC-V tree as IIRC we're
> using it too.
Hi Palmer, there is a v3 with changelog updated,
https://lore.kernel.org/lkml/20210731025057.78825-1-wangliang101@huawei.com/
>
> Thanks!
> .
>
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: [PATCH v2] lib: Use PFN_PHYS() in devmem_is_allowed()
@ 2021-08-04 5:03 ` Kefeng Wang
0 siblings, 0 replies; 12+ messages in thread
From: Kefeng Wang @ 2021-08-04 5:03 UTC (permalink / raw)
To: Palmer Dabbelt
Cc: wangliang101, mcgrof, linux-kernel, Greg KH, linux,
linux-arm-kernel, stable, wangle6, kepler.chenxin, nixiaoming
On 2021/8/4 8:20, Palmer Dabbelt wrote:
> On Fri, 30 Jul 2021 00:04:05 PDT (-0700), wangkefeng.wang@huawei.com
> wrote:
>>
>> On 2021/7/30 14:49, Liang Wang wrote:
>>> The physical address may exceed 32 bits on ARM(when ARM_LPAE enabled),
>>> use PFN_PHYS() in devmem_is_allowed(), or the physical address may
>>> overflow and be truncated.
>>>
>>> This bug was initially introduced from v2.6.37, and the function was
>>> moved
>>> to lib when v5.10.
>>>
>>> Fixes: 087aaffcdf9c ("ARM: implement CONFIG_STRICT_DEVMEM by
>>> disabling access to RAM via /dev/mem")
>>> Fixes: 527701eda5f1 ("lib: Add a generic version of
>>> devmem_is_allowed()")
>>> Cc: stable@vger.kernel.org # v2.6.37
>>> Signed-off-by: Liang Wang <wangliang101@huawei.com>
>> Reviewed-by: Kefeng Wang <wangkefeng.wang@huawei.com>
>>> ---
>>> v2: update subject and changelog
>>> lib/devmem_is_allowed.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
...
> Acked-by: Palmer Dabbelt <palmerdabbelt@google.com>
>
> I only see the reply so I'm assuming this is going in through some
> other tree, but LMK if you want it via the RISC-V tree as IIRC we're
> using it too.
Hi Palmer, there is a v3 with changelog updated,
https://lore.kernel.org/lkml/20210731025057.78825-1-wangliang101@huawei.com/
>
> Thanks!
> .
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2021-08-04 5:04 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-07-30 7:43 [PATCH v2] lib: Use PFN_PHYS() in devmem_is_allowed() Liang Wang
2021-07-30 7:43 ` Liang Wang
2021-07-30 19:36 ` Luis Chamberlain
2021-07-30 19:36 ` Luis Chamberlain
2021-07-31 2:04 ` 答复: " wangliang (C)
2021-07-31 2:04 ` wangliang (C)
[not found] <20210730064915.56249-1-wangliang101@huawei.com>
2021-07-30 7:04 ` Kefeng Wang
2021-07-30 7:04 ` Kefeng Wang
2021-08-04 0:20 ` Palmer Dabbelt
2021-08-04 0:20 ` Palmer Dabbelt
2021-08-04 5:03 ` Kefeng Wang
2021-08-04 5:03 ` Kefeng Wang
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.