linux-kernel - Re: Re: Re: [RFC] PAGE_RW Should be added to PAGE

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]

Message-ID: <Pine.LNX.4.64.0609150514190.7397@blonde.wat.veritas.com>
Date:	Fri, 15 Sep 2006 05:30:18 +0100 (BST)
From:	Hugh Dickins <hugh@...itas.com>
To:	Yingchao Zhou <yc_zhou@...c.ac.cn>
cc:	linux-kernel <linux-kernel@...r.kernel.org>, akpm <akpm@...l.org>,
	alan <alan@...hat.com>, zxc <zxc@...c.ac.cn>
Subject: Re: Re: Re: [RFC] PAGE_RW Should be added to PAGE_COPY ?

On Fri, 15 Sep 2006, Yingchao Zhou wrote:
> >On Fri, 15 Sep 2006, Yingchao Zhou wrote:
> >> It's ok to mmap MAP_SHARED. But is it not a normal way to malloc() a space and
> >> then registered to NIC ?
> >
> >Not that I know of.  How would one register malloc()ed space to a NIC?
> >Sorry, I may well be misunderstanding you.
> The user-level NIC does this, eg. Myrinet...

Okay, thanks, I know nothing of that, and must defer to those who do.

But it sounds broken to me, in the way that you have described.

And the fix would not be to change the kernel's semantics for private
mappings, but for the app to use a shared mapping instead of a private.

Which would indeed be more work for the app than just using malloc,
since it needs some memory object (e.g. tmpfs file?) to map shared.

Hugh
-
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/