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]

Date:	Thu, 11 Feb 2010 08:43:32 +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,

On 02/11/2010 12:02 AM, Miklos Szeredi wrote:
>> 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.
> 
> What I really meant was: does it ever happen that mapping a *single
> open file* of a chardev twice will result in two different maps?
> Or will the maps be only different if it was a different open of the
> device?

I don't know if there is one but ->mmap() implementation is definitely
allowed to do that.

> If there's a pattern there, we might make the sharing/non-sharing
> automated, and greatly simplify the interface.

Isn't the interface pretty simple as it is?  If we want to make it
easier for API users by imposing limits, I think the correct layer to
do that would be at the library level.

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/