linux-kernel - Re: [fuse-devel] [PATCH] FUSE/CUSE: implement direct mmap support

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 for Android: free password hash cracker in your pocket

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

Message-ID: <4B73FCF2.3020108@kernel.org>
Date:	Thu, 11 Feb 2010 21:49:54 +0900
From:	Tejun Heo <tj@...nel.org>
To:	Miklos Szeredi <miklos@...redi.hu>
CC:	mszeredi@...e.cz, linux-kernel@...r.kernel.org,
	fuse-devel@...ts.sourceforge.net, polynomial-c@...too.org,
	akpm@...ux-foundation.org
Subject: Re: [fuse-devel] [PATCH] FUSE/CUSE: implement direct mmap support

Hello, Miklos.

On 02/11/2010 09:25 PM, Miklos Szeredi wrote:
>> If the server wants the two regions to be separate, it can map it to
>> say 5-11 and returnt he offset of 5.  If it wants them to be shared,
>> it will have to mmap 1-2 and 6-7 and return offset of 1.
> 
> What if region 6-7 is already occupied (e.g. because a separate region
> was put there)?

Allocating and managing the address space ranges are the server's
responsibility.  If it expects the region to grow, it shouldn't
colocate those regions.  The kernel is just giving the server an
address space to manage and letting it redirect mmaps to arbitrary
(sans the SHMLBA alignment restriction) part of it.  The rest is upto
the server.

Thanks.

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