linux-kernel - Re: IO space memcpy support for userspace.

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:	Fri, 5 Dec 2008 12:32:04 -0500
From:	"Carlos O'Donell" <carlos@...temhalted.org>
To:	"Dave Airlie" <airlied@...il.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	libc-alpha@...rces.redhat.com
Subject: Re: IO space memcpy support for userspace.

On Thu, Dec 4, 2008 at 10:40 PM, Dave Airlie <airlied@...il.com> wrote:
> I'm sure this has come up before and I'm sure I'll either wish I never
> posted this or someone will show me the crisp corpse of the last guy
> who suggested it.

Do you plan to prevent the compiler from issuing the same sorts of
instructions that might appear in an optimized memcpy?

Isn't it dangerous to have memory that doesn't behave like normal
memory, and yet try to treat it like normal memory?

This mismatch of abstractions is a warning that must not be ignored.

IMHO you need a thin library with a new API (adding support for HAL
would be a clever way to check for PCI devices and perhaps even
mappings).

Cheers,
Carlos.
--
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/