| 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: <49F16786.7010401@petalogix.com> Date: Fri, 24 Apr 2009 09:17:26 +0200 From: Michal Simek <michal.simek@...alogix.com> To: Christoph Hellwig <hch@....de> CC: linux-arch@...r.kernel.org, microblaze-uclinux@...e.uq.edu.au, linux-kernel@...r.kernel.org, Matthew Wilcox <matthew@....cx> Subject: Re: USE_ELF_CORE_DUMP? Christoph Hellwig wrote: > Currently all architectures but microblaze unconditionally define > USE_ELF_CORE_DUMP. The microblaze ommision seems like an error to > me, so can we just kill this ifdef and make sure we are the same > everywhere? > Where did you find it? I haven't seen in in mainline (noMMU kernel). It is in my MMU patches which I want to send for review soon. For noMMU I use CONFIG_BINFMT_FLAT (binfmt_flat.c) where I don't need USE_ELF_CORE_DUMP For MMU I use CONFIG_BINFMT_ELF (binfmt_elf.c) where USE_ELF_CORE_DUMP make sense to me. Can you give me some clue what you are trying to fix? Thanks, Michal > -- > To unsubscribe from this list: send the line "unsubscribe linux-arch" in > the body of a message to majordomo@...r.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- Michal Simek, Ing. (M.Eng) PetaLogix - Linux Solutions for a Reconfigurable World w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663 -- 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