On Mon, 2014-12-01 at 16:24 +1100, Paul Mackerras wrote:
On Mon, Dec 01, 2014 at 04:02:14PM +1100, Michael Ellerman wrote:
On Mon, 2014-12-01 at 15:28 +1100, Paul Mackerras wrote:
The bounds check for nodeid in cache_alloc_node gives false
positives on machines where the node IDs are
On 12/1/14 6:28 AM, Paul Mackerras wrote:
---
v2: include the oops message in the patch description
mm/slab.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/slab.c b/mm/slab.c
index eb2b2ea..f34e053 100644
--- a/mm/slab.c
+++ b/mm/slab.c
@@ -3076,7 +3076,7 @@ static
On Mon, 1 Dec 2014, Paul Mackerras wrote:
The bounds check for nodeid in cache_alloc_node gives false
positives on machines where the node IDs are not contiguous, leading
to a panic at boot time. For example, on a POWER8 machine the node
IDs are typically 0, 1, 16 and 17. This means
The bounds check for nodeid in cache_alloc_node gives false
positives on machines where the node IDs are not contiguous, leading
to a panic at boot time. For example, on a POWER8 machine the node
IDs are typically 0, 1, 16 and 17. This means that num_online_nodes()
returns 4, so when
(2014/12/01 13:28), Paul Mackerras wrote:
The bounds check for nodeid in cache_alloc_node gives false
positives on machines where the node IDs are not contiguous, leading
to a panic at boot time. For example, on a POWER8 machine the node
IDs are typically 0, 1, 16 and 17. This means that
On Mon, 2014-12-01 at 15:28 +1100, Paul Mackerras wrote:
The bounds check for nodeid in cache_alloc_node gives false
positives on machines where the node IDs are not contiguous, leading
to a panic at boot time. For example, on a POWER8 machine the node
IDs are typically 0, 1, 16 and 17.
On Mon, Dec 01, 2014 at 04:02:14PM +1100, Michael Ellerman wrote:
On Mon, 2014-12-01 at 15:28 +1100, Paul Mackerras wrote:
The bounds check for nodeid in cache_alloc_node gives false
positives on machines where the node IDs are not contiguous, leading
to a panic at boot time. For
