linux-kernel - Re: [fuse-devel] OSS Proxy Jack slave

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, 10 Jun 2010 15:28:08 +0200
From:	Miklos Szeredi <miklos@...redi.hu>
To:	Tejun Heo <tj@...nel.org>
CC:	miklos@...redi.hu, hmajxxlh@...bac.com,
	fuse-devel@...ts.sourceforge.net, mszeredi@...e.cz,
	linux-kernel@...r.kernel.org
Subject: Re: [fuse-devel] OSS Proxy Jack slave

On Thu, 10 Jun 2010, Tejun Heo wrote:
> Hello,
> 
> Nope, it's not required for osspd but it's a rather strong
> limitation on the interface which would be pretty difficult to work
> around later.  Page protection tricks would be very cumbersome and
> unscalable.  Hmmm, it does remove the necessity for allocating
> kernel pages, right?  Still, it seems like a big limitation.  Are
> you sure this is a good idea?

I'm sure its a good idea to provide an interface that does't _require_
server side mmaps.  This doesn't preclude an mmap interface later on,
but I'd rather start with a "pure" read/write device interface, which
is in a lot of ways simpler to solve than mmap.

As for pinning kernel pages, I still think it's a good idea for the
char device interface, but you're right, it's not necessary.

In fact I'm mostly ready with an implementation of store/retrieve that
just pokes the regular page cache.

Thanks,
Miklos
--
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/