Out of memory condition is not a bug and while we can't add new memory in
such case crashing the system seems wrong. Propagating the return value
from register_memory_resource() requires interface change.

Signed-off-by: Vitaly Kuznetsov <[email protected]>
Cc: Andrew Morton <[email protected]>
Cc: David Rientjes <[email protected]>
Cc: Tang Chen <[email protected]>
Cc: Naoya Horiguchi <[email protected]>
Cc: Xishi Qiu <[email protected]>
Cc: Sheng Yong <[email protected]>
Cc: Zhu Guihua <[email protected]>
Cc: Dan Williams <[email protected]>
Cc: David Vrabel <[email protected]>
Cc: Igor Mammedov <[email protected]>
---
Changes since v1:
- Use ERR_PTR/PTR_ERR/IS_ERR() [David Rientjes]
---
 mm/memory_hotplug.c | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index a042a9d..92f9595 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -131,7 +131,8 @@ static struct resource *register_memory_resource(u64 start, 
u64 size)
 {
        struct resource *res;
        res = kzalloc(sizeof(struct resource), GFP_KERNEL);
-       BUG_ON(!res);
+       if (!res)
+               return ERR_PTR(-ENOMEM);
 
        res->name = "System RAM";
        res->start = start;
@@ -140,7 +141,7 @@ static struct resource *register_memory_resource(u64 start, 
u64 size)
        if (request_resource(&iomem_resource, res) < 0) {
                pr_debug("System RAM resource %pR cannot be added\n", res);
                kfree(res);
-               res = NULL;
+               return ERR_PTR(-EEXIST);
        }
        return res;
 }
@@ -1312,8 +1313,8 @@ int __ref add_memory(int nid, u64 start, u64 size)
        int ret;
 
        res = register_memory_resource(start, size);
-       if (!res)
-               return -EEXIST;
+       if (IS_ERR(res))
+               return PTR_ERR(res);
 
        ret = add_memory_resource(nid, res);
        if (ret < 0)
-- 
2.4.3

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

Reply via email to