ACPI, APEI Fix the return value(==NULL) of acpi_pre_map().
PATCH 1/2 ACPI, APEI Fix the return value(==NULL) of acpi_pre_map().
acpi_pre_map() is used for remapping the physical address of I/O, so it should be return NULL or remapped virtual address. The problem is that when (paddr - pg_off) equals 0, no matter whether I/O remapping is successful or not, the function returns NULL.
In acpi_pre_map(), after the physical address is remapped successfully, it will check whether the physical address has been added into acpi_iomaps list again.
- If the physical address has been added into acpi_iomaps, the virtual address will be saved in vaddr.
- Otherwise, NULL be saved in vaddr.
So if the physical address is the first time to be remapped, vaddr will be NULL always.
In many cases, (paddr - pg_off) may not equal 0. So the function could work well. In our machine, (paddr - pg_off) equals 0, so the return value of acpi_pre_map() is NULL.
This patch fixed it and I confirmed it on x86_64 next-tree.
v2:
Modified the unsuitable description of patch.
v3:
Modified the wrong words in the description of patch.
--- drivers/acpi/atomicio.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)
drivers/acpi/atomicio.c +2 -2
@@ -133,7 +133,7 @@ static void __iomem *acpi_pre_map(phys_addr_t paddr,spin_lock_irqsave (&acpi_iomaps_lock, flags); vaddr =__acpi_try_ioremap (paddr, size); -if (vaddr) { +if (unlikely (vaddr)) {spin_unlock_irqrestore (&acpi_iomaps_lock, flags);iounmap (map->vaddr);kfree (map);
@@ -142,7 +142,7 @@ static void __iomem *acpi_pre_map(phys_addr_t paddr,list_add_tail_rcu (&map->list, &acpi_iomaps);spin_unlock_irqrestore (&acpi_iomaps_lock, flags); -return vaddr + (paddr - pg_off); +return map->vaddr + (paddr - pg_off); err_unmap:iounmap (vaddr);return NULL ;
-- 1.7.1.
Quoted 12 lines · Jin Dongming
acpi_pre_map()is used for remapping the physical address of I/O, so it should be return NULL or remapped virtual address. The problem is that when (paddr -pg_off) equals 0, no matter whether I/O remapping is successful or not, the function returns NULL.In
acpi_pre_map(), after the physical address is remapped successfully, it will check whether the physical address has been added intoacpi_iomapslist again.
- If the physical address has been added intoacpi_iomaps, the virtual address will be saved in vaddr.
- Otherwise, NULL be saved in vaddr.
Quoted 8 lines
So if the physical address is the first time to be remapped, vaddr will be NULL always.
In many cases, (paddr -
pg_off) may not equal 0. So the function could work well. In our machine, (paddr -pg_off) equals 0, so the return value ofacpi_pre_map()is NULL.This patch fixed it and I confirmed it on
x86_64next-tree.
This description is complicated and obscures the very simple bug you are fixing. I suggest something like this:
ACPI: fix acpi_pre_map() return value
After we ioremap() a new region, we call __acpi_try_ioremap() to see whether another thread has already mapped the same region. This check clobbers "vaddr", so compute the return value using the ioremap() result "map->vaddr" instead.
Quoted 17 lines
v2:
Modified the unsuitable description of patch.v3:
Modified the wrong words in the description of patch.Signed-off-by Jin Dongming <[email protected]>Acked-by Huang Ying <[email protected]>--- drivers/acpi/atomicio.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)drivers/acpi/atomicio.c +0
-0
drivers/acpi/atomicio.c static void __iomem *acpi_pre_map(phys_addr_t paddr, · line 136
Quoted 5 lines
drivers/acpi/atomicio.c +1
-1@@ -133,7 +133,7 @@ static void __iomem *acpi_pre_map(phys_addr_t paddr,spin_lock_irqsave (&acpi_iomaps_lock, flags); vaddr =__acpi_try_ioremap (paddr, size); -if (vaddr) { +if (unlikely (vaddr)) {
This "unlikely" addition also obscures things. It's completely unrelated to the bug you're fixing, so it should be in a different patch, and I'm dubious that there's enough performance advantage to compensate for the decreased code readability. I wouldn't make this change unless you can measure a performance improvement.
drivers/acpi/atomicio.c static void __iomem *acpi_pre_map(phys_addr_t paddr, · line 145
Quoted 9 lines
drivers/acpi/atomicio.c +1
-1spin_unlock_irqrestore (&acpi_iomaps_lock, flags);iounmap (map->vaddr);kfree (map);@@ -142,7 +142,7 @@ static void __iomem *acpi_pre_map(phys_addr_t paddr,list_add_tail_rcu (&map->list, &acpi_iomaps);spin_unlock_irqrestore (&acpi_iomaps_lock, flags); -return vaddr + (paddr - pg_off); +return map->vaddr + (paddr - pg_off);
Since you're changing this line anyway, I think you should change it to:
return map->vaddr + (paddr - map->paddr);
so it matches __acpi_try_ioremap().
Quoted 10 lines
drivers/acpi/atomicio.c +0
-2err_unmap:iounmap (vaddr);return NULL ; -- 1.7.1. --To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi, Bjorn Helgaas
I will modify this patch and resend it as soon as possible in next week.
Best Regards,
Jin Dongming
Quoted 94 lines · Bjorn Helgaas
Quoted 12 lines · Jin Dongming
acpi_pre_map()is used for remapping the physical address of I/O, so it should be return NULL or remapped virtual address. The problem is that when (paddr -pg_off) equals 0, no matter whether I/O remapping is successful or not, the function returns NULL.In
acpi_pre_map(), after the physical address is remapped successfully, it will check whether the physical address has been added intoacpi_iomapslist again.
- If the physical address has been added intoacpi_iomaps, the virtual address will be saved in vaddr.
- Otherwise, NULL be saved in vaddr.Quoted 8 lines
So if the physical address is the first time to be remapped, vaddr will be NULL always.
In many cases, (paddr -
pg_off) may not equal 0. So the function could work well. In our machine, (paddr -pg_off) equals 0, so the return value ofacpi_pre_map()is NULL.This patch fixed it and I confirmed it on
x86_64next-tree.This description is complicated and obscures the very simple bug you are fixing. I suggest something like this:
ACPI: fix
acpi_pre_map()return valueAfter we
ioremap()a new region, we call__acpi_try_ioremap()to see whether another thread has already mapped the same region. This check clobbers "vaddr", so compute the return value using theioremap()result "map->vaddr" instead.Quoted 17 lines
v2:
Modified the unsuitable description of patch.v3:
Modified the wrong words in the description of patch.Signed-off-by Jin Dongming <[email protected]>Acked-by Huang Ying <[email protected]>--- drivers/acpi/atomicio.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)drivers/acpi/atomicio.c +0
-0drivers/acpi/atomicio.c static void __iomem *acpi_pre_map(phys_addr_t paddr, · line 136
Quoted 5 lines
drivers/acpi/atomicio.c +1
-1@@ -133,7 +133,7 @@ static void __iomem *acpi_pre_map(phys_addr_t paddr,spin_lock_irqsave (&acpi_iomaps_lock, flags); vaddr =__acpi_try_ioremap (paddr, size); -if (vaddr) { +if (unlikely (vaddr)) {This "unlikely" addition also obscures things. It's completely unrelated to the bug you're fixing, so it should be in a different patch, and I'm dubious that there's enough performance advantage to compensate for the decreased code readability. I wouldn't make this change unless you can measure a performance improvement.
drivers/acpi/atomicio.c static void __iomem *acpi_pre_map(phys_addr_t paddr, · line 145
Quoted 9 lines
drivers/acpi/atomicio.c +1
-1spin_unlock_irqrestore (&acpi_iomaps_lock, flags);iounmap (map->vaddr);kfree (map);@@ -142,7 +142,7 @@ static void __iomem *acpi_pre_map(phys_addr_t paddr,list_add_tail_rcu (&map->list, &acpi_iomaps);spin_unlock_irqrestore (&acpi_iomaps_lock, flags); -return vaddr + (paddr - pg_off); +return map->vaddr + (paddr - pg_off);Since you're changing this line anyway, I think you should change it to:
return map->vaddr + (paddr - map->paddr);so it matches
__acpi_try_ioremap().Quoted 10 lines
drivers/acpi/atomicio.c +0
-2err_unmap:iounmap (vaddr);return NULL ; -- 1.7.1. --To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/