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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <4B72A802.6040009@kernel.org>
Date:	Wed, 10 Feb 2010 21:35:14 +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/10/2010 09:15 PM, Miklos Szeredi wrote:
>> Same offset -> same page doesn't hold.
> 
> Right, I really meant same page -> same offset.  If the same offset is
> mapped to multiple pages: no problem.  If the same page is mapped to
> multiple offsets, then obviously it's not going to work properly.

Yeap.

>> Can you please elaborate how you think the thing can work without
>> referencing the proposed implementation?  Let's find out where the
>> misundertanding is.
> 
> Thinking about it I'm not really sure...
> 
> Maybe the problem is that the propsed solution allows too much
> freedom.  Normally there's a 1:1 relationship between pages and
> offsets.  But we want to break that for CUSE, because two different
> mappings of a char dev might point to completely different pages,
> right?

Yeap.  It basically behaves like each mmap() instance is a shm
instance and the offset into dmmap_regions is the shmkey.

> When does that happen?  Can it happen that two mappings of the same
> file descriptor will have different backing pages?

Yeah, sure.  FUSE server is free to give them separate regions.  The
only restriction is the SHMLBA alignment which is pretty easy to
adhere to.

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/