| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <4D1BF056.3060909@lwfinger.net> Date: Wed, 29 Dec 2010 20:37:10 -0600 From: Larry Finger <Larry.Finger@...inger.net> To: Mario 'BitKoenig' Holbe <Mario.Holbe@...Ilmenau.DE>, LKML <linux-kernel@...r.kernel.org>, wireless <linux-wireless@...r.kernel.org>, b43-dev <b43-dev@...ts.infradead.org> Subject: Re: 2.6.37-rc7: Regression: b43: crashes in hwrng_register() On 12/29/2010 07:20 PM, Mario 'BitKoenig' Holbe wrote: > > It will surely not matter: if CONFIG_B43_HWRNG would not have been > defined, hwrng_register() would not have been reached in the dump from > my first mail. > > If you really like me to try that patch, I'll do so when I'm awake again > and will then answer you that nothing has changed :) No, don't bother. I do have a different request. The byte counts for my 32-bit system do not match yours. Could you please use the following command to find the instructions that are failing? objdump -l -d drivers/char/hw_random/core.o | less Use the search to find the start of hwrng_register, then add 0x4c to the starting address. Once I see hte instruction that is failing, I should be able to find where the failure occurs. The order in which things are registered should not cause an error, but who knows? Larry -- 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