Messages in this thread |  | | Date | Thu, 18 Mar 2010 18:30:54 +0200 | Subject | Re: [BUG] SLOB breaks Crypto | From | Pekka Enberg <> |
| |
On Mon, Mar 15, 2010 at 3:39 PM, <michael-dev@fami-braun.de> wrote: > Hi, > > I've been trying to get Linux Kernel Crypto up&running > on an AMD Geode LX board (Alix 2d2) but instantly > experienced a huge amount of errors that look much like > general memory corruption. Among them where NULL-pointer errors in > net/core/dst.c, ath9k_skb_.*, net_skb.*, page table corruption, > NULL-pointer errors in add_swap.* (with no swap installed at all) and > many more. These errors could be trigger by loading tcrypt for any > installed algorithm severeal times or by loading tcrypt without > paramters or by compiling crypto statically into the kernel or by > installing and loading cryptodev or ocf-linux. > > I've had the system configured with SLOB and all memory debugging > enabled. All of these errors instantly disappeared when switching back > to SLAB.
Even with CONFIG_DEBUG_SLAB enabled or with CONFIG_SLUB and CONFIG_SLUB_DEBUG_ON?
|  |