linux-kernel - alacrityvm-next: clearly specify ioq endianness

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1260305854-31472-1-git-send-email-iws@ovro.caltech.edu>
Date:	Tue,  8 Dec 2009 12:57:29 -0800
From:	"Ira W. Snyder" <iws@...o.caltech.edu>
To:	alacrityvm-devel@...ts.sourceforge.net,
	linux-kernel@...r.kernel.org
Subject: alacrityvm-next: clearly specify ioq endianness

This is a respin of the previous patch series against alacrityvm.git's
linux-next branch, to facilitate easier merging with the linux-next tree.

The SHM_SIGNAL and IOQ code is meant to be used for communication channels
between systems with different bit widths and operating systems.
Conceivably, this could include systems with different endianness as well,
for example, using QEMU on x86 to emulate a powerpc.

This patch series annotates all shared structures as little endian, and
fixes up all users. This means that there is no overhead in the most common
case, x86-on-x86. The byteswaps compile out.

[RESEND: added LKML to CC per Greg Haskins' request]

 drivers/net/vbus-enet.c    |   36 ++++++++++++++++++------------------
 drivers/vbus/bus-proxy.c   |    2 +-
 drivers/vbus/pci-bridge.c  |   18 +++++++++---------
 include/linux/ioq.h        |   24 ++++++++++++------------
 include/linux/shm_signal.h |    8 ++++----
 lib/ioq.c                  |   28 ++++++++++++++++------------
 6 files changed, 60 insertions(+), 56 deletions(-)

Thanks,
Ira
--
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/