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
| ||
|
Date: Fri, 17 Jul 2015 10:36:10 +0530 From: Sudip Mukherjee <sudipm.mukherjee@...il.com> To: Andrew Morton <akpm@...ux-foundation.org> Cc: David Howells <dhowells@...hat.com>, linux-kernel@...r.kernel.org, Ananth N Mavinakayanahalli <ananth@...ibm.com>, Anil S Keshavamurthy <anil.s.keshavamurthy@...el.com>, Masami Hiramatsu <masami.hiramatsu.pt@...achi.com> Subject: Re: [PATCH v2 1/7] mn10300: fix build failure On Thu, Jul 16, 2015 at 02:54:26PM -0700, Andrew Morton wrote: > On Thu, 18 Jun 2015 17:47:47 +0530 Sudip Mukherjee <sudipm.mukherjee@...il.com> wrote: > > > So an appropriate fix for this would be to move the references to > prev_kprobe/kprobe_ctlblk out of include/linux/kprobes.h and into > asm/kprobes.h. Presumably via include/asm-generic/kprobes.h in some > fashion. > > Have you tested this patch on mn10300? Does kprobes actually work on > mn10300? Perhaps not, and the solution here is to disable kprobes on > that arch until someone fixes it all up. No, this was not tested on board. :( I tried my best to get a board but it seems board sellers in India have not even heard the name of "mn10300". I tried contacting Koichi Yasutake (one of the maintainer of mn10300) in hope of getting/buying a board, but email of Koichi Yasutake is bouncing. I tried to contact the company about one of their board and the following is their reply: "As you say, linux runs on MN103E0700. But MN103E0700 is now EOL, so we need not to maintenace linux." :( > > > Please resend any mn10300 fixes which you still have pending. Should i resend as it is or should i fix according to your suggestion? or since this is arch specific changes and not tested on board so if you want it can be dropped also. > Please be a bit more sparing in the cc's when doing so ;) yes, cc became a long list but it was also improper to send some part of the series to few maintainer and other to some other maintainers. regards sudip -- 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