[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20150322.195403.1653355516554747742.davem@davemloft.net>
Date: Sun, 22 Mar 2015 19:54:03 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: david.ahern@...cle.com
Cc: torvalds@...ux-foundation.org, sparclinux@...r.kernel.org,
linux-mm@...ck.org, linux-kernel@...r.kernel.org, bpicco@...oft.net
Subject: Re: 4.0.0-rc4: panic in free_block
From: David Ahern <david.ahern@...cle.com>
Date: Sun, 22 Mar 2015 17:35:49 -0600
> I don't know if you caught Bob's message; he has a hack to bypass
> memcpy and memmove in mm/slab.c use a for loop to move entries. With
> the hack he is not seeing the problem.
>
> This is the hack:
>
> +static void move_entries(void *dest, void *src, int nr)
> +{
> + unsigned long *dp = dest;
> + unsigned long *sp = src;
> +
> + for (; nr; nr--, dp++, sp++)
> + *dp = *sp;
> +}
> +
>
> and then replace the mempy and memmove calls in transfer_objects,
> cache_flusharray and drain_array to use move_entries.
>
> I just put it on 4.0.0-rc4 and ditto -- problem goes away, so it
> clearly suggests the memcpy or memmove are the root cause.
Thanks, didn't notice that.
So, something is amuck.
--
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