| 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: <1295474423.12215.1612.camel@gandalf.stny.rr.com> Date: Wed, 19 Jan 2011 17:00:23 -0500 From: Steven Rostedt <rostedt@...dmis.org> To: David Miller <davem@...emloft.net> Cc: mathieu.desnoyers@...icios.com, richm@...elvet.org.uk, 609371@...s.debian.org, ben@...adent.org.uk, sparclinux@...r.kernel.org, linux-kernel@...r.kernel.org, fweisbec@...il.com, mingo@...hat.com Subject: Re: Bug#609371: linux-image-2.6.37-trunk-sparc64: module scsi_mod: Unknown relocation: 36 On Wed, 2011-01-19 at 13:40 -0800, David Miller wrote: > My concern is that if there is ever a u64 or similarly "long long" > typed member in these tracing structures, it will not be aligned > sufficiently to avoid unaligned access traps on 32-bit systems. The structure that gets placed in this section is the ftrace_event_call. It consists only of pointers, a struct list_head, a couple of "int", and a struct trace_event, which consists of: a struct hlist_node, a struct list_head, an int, and a pointer. None of these are more than "long" and I don't foresee them needing a long long type. I think assuming that a long is the largest item should due. We can add a comment next to these structures specifying this dependency, and hopefully it would be updated if we ever do include a long long in them. -- Steve -- 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