[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080211114818.74c9dcc7.akpm@linux-foundation.org>
Date: Mon, 11 Feb 2008 11:48:18 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Badari Pulavarty <pbadari@...ibm.com>
Cc: linux-kernel@...r.kernel.org, greg@...ah.com, haveblue@...ibm.com,
linux-mm@...ck.org
Subject: Re: [-mm PATCH] register_memory/unregister_memory clean ups
On Mon, 11 Feb 2008 09:23:18 -0800
Badari Pulavarty <pbadari@...ibm.com> wrote:
> Hi Andrew,
>
> While testing hotplug memory remove against -mm, I noticed
> that unregister_memory() is not cleaning up /sysfs entries
> correctly. It also de-references structures after destroying
> them (luckily in the code which never gets used). So, I cleaned
> up the code and fixed the extra reference issue.
>
> Could you please include it in -mm ?
>
> Thanks,
> Badari
>
> register_memory()/unregister_memory() never gets called with
> "root". unregister_memory() is accessing kobject_name of
> the object just freed up. Since no one uses the code,
> lets take the code out. And also, make register_memory() static.
>
> Another bug fix - before calling unregister_memory()
> remove_memory_block() gets a ref on kobject. unregister_memory()
> need to drop that ref before calling sysdev_unregister().
>
I'd say this:
> Subject: [-mm PATCH] register_memory/unregister_memory clean ups
is rather tame. These are more than cleanups! These sound like
machine-crashing bugs. Do they crash machines? How come nobody noticed
it?
All very strange...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists