linux-kernel - Re: Why get/put_unaligned are hidden behind #ifdef __KERNEL_

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 31 Oct 2010 19:10:37 +0300
From:	Igor Zhbanov <izh1979@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: Why get/put_unaligned are hidden behind #ifdef __KERNEL__ on
 PowerPC and Microblaze?

2010/10/31 Andreas Schwab <schwab@...ux-m68k.org>:
>
> Since <asm/unaligned.h> is not an exported header the point is moot.

And why not to export <asm/unaligned.h>? I think it will be useful to
have unified mechanism
for unaligned memory access in users pace. There are numerous
libraries that deal
with binary file formats with unaligned structure fields. Also there
are some network
protocols with unaligned fields of packets.

I think that unaligned memory access interface are stable, so it can
be safely exported
to user space. We have some other platform-related exported headers,
e.g. <asm/byteorder.h>,
so why not to export <asm/unaligned.h>. Let it be "official" way to
deal with unaligned data
in user space too.
--
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/