From: Michael Bringmann <hidden> Date: 2017-05-22 20:44:46
When adding or removing memory, the aa_index (affinity value) for the
memblock must also be converted to match the endianness of the rest
of the 'ibm,dynamic-memory' property. Otherwise, subsequent retrieval
of the attribute will likely lead to non-existent nodes, followed by
using the default node in the code inappropriately.
Signed-off-by: Michael Bringmann <redacted>
---
arch/powerpc/platforms/pseries/hotplug-memory.c | 2 ++
1 file changed, 2 insertions(+)
From: Michael Ellerman <mpe@ellerman.id.au> Date: 2017-05-30 11:42:05
Michael Bringmann [off-list ref] writes:
quoted hunk
When adding or removing memory, the aa_index (affinity value) for the
memblock must also be converted to match the endianness of the rest
of the 'ibm,dynamic-memory' property. Otherwise, subsequent retrieval
of the attribute will likely lead to non-existent nodes, followed by
using the default node in the code inappropriately.
Signed-off-by: Michael Bringmann <redacted>
AFAICS this code was added in commit 5f97b2a0d176 ("powerpc/pseries:
Implement memory hotplug add in the kernel").
So this should probably be marked:
Fixes: 5f97b2a0d176 ("powerpc/pseries: Implement memory hotplug add in the kernel")
And it seems like a bug we'd want fixed in stable, so:
Cc: stable@vger.kernel.org # v4.1+
Am I right?
cheers
When adding or removing memory, the aa_index (affinity value) for the
memblock must also be converted to match the endianness of the rest
of the 'ibm,dynamic-memory' property. Otherwise, subsequent retrieval
of the attribute will likely lead to non-existent nodes, followed by
using the default node in the code inappropriately.
Signed-off-by: Michael Bringmann <redacted>
AFAICS this code was added in commit 5f97b2a0d176 ("powerpc/pseries:
Implement memory hotplug add in the kernel").
So this should probably be marked:
Fixes: 5f97b2a0d176 ("powerpc/pseries: Implement memory hotplug add in the kernel")
And it seems like a bug we'd want fixed in stable, so:
Cc: stable@vger.kernel.org # v4.1+
Am I right?
From: Michael Ellerman <mpe@ellerman.id.au> Date: 2017-05-31 04:03:27
Nathan Fontenot [off-list ref] writes:
On 05/30/2017 06:41 AM, Michael Ellerman wrote:
quoted
Michael Bringmann [off-list ref] writes:
quoted
When adding or removing memory, the aa_index (affinity value) for the
memblock must also be converted to match the endianness of the rest
of the 'ibm,dynamic-memory' property. Otherwise, subsequent retrieval
of the attribute will likely lead to non-existent nodes, followed by
using the default node in the code inappropriately.
Signed-off-by: Michael Bringmann <redacted>
AFAICS this code was added in commit 5f97b2a0d176 ("powerpc/pseries:
Implement memory hotplug add in the kernel").
So this should probably be marked:
Fixes: 5f97b2a0d176 ("powerpc/pseries: Implement memory hotplug add in the kernel")
And it seems like a bug we'd want fixed in stable, so:
Cc: stable@vger.kernel.org # v4.1+
Am I right?
From: Michael Ellerman <hidden> Date: 2017-06-01 13:31:11
On Mon, 2017-05-22 at 20:44:37 UTC, Michael Bringmann wrote:
When adding or removing memory, the aa_index (affinity value) for the
memblock must also be converted to match the endianness of the rest
of the 'ibm,dynamic-memory' property. Otherwise, subsequent retrieval
of the attribute will likely lead to non-existent nodes, followed by
using the default node in the code inappropriately.
Signed-off-by: Michael Bringmann <redacted>