linux-kernel - Re: [PATCHSET] FUSE: extend FUSE to support more operations

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: <491C2A63.1030804@kernel.org>
Date:	Thu, 13 Nov 2008 22:23:47 +0900
From:	Tejun Heo <tj@...nel.org>
To:	Miklos Szeredi <miklos@...redi.hu>
CC:	fuse-devel@...ts.sourceforge.net, greg@...ah.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCHSET] FUSE: extend FUSE to support more operations

Hi,

Miklos Szeredi wrote:
>> Hmm... yeah, allocating handle from kernel should work fine, but I
>> wouldn't worry about race here.  We can just use 64 bit and guarantee
>> that any handle won't be reused ever.
> 
> Btw, the protocol could be simplified even more by getting rid of all
> acknowledgements:
> 
> <- POLL-request(pollhandle) (alloc handle)
> ...
> -> POLL-notification(pollhandle)
> ...
> <- POLL_RELEASE(pollhandle)
> 
> So normally ->poll() wouldn't have to sleep at all.  If the POLL
> request fails for some reason, userspace just sends a notification
> with the respective error.

We don't need POLL_RELEASE but we still need POLL-reply (to request) to
send revents.  We can put that into notification too.  Hmmm... Yeah,
that could be simpler for FUSE servers.  I'll venture that way.

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/