linux-kernel - Re: [PATCHSET] CUSE: implement CUSE, take #3

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] [day] [month] [year] [list]

Message-ID: <4A04C1A8.2070904@kernel.org>
Date:	Sat, 09 May 2009 08:35:04 +0900
From:	Tejun Heo <tj@...nel.org>
To:	Miklos Szeredi <miklos@...redi.hu>
CC:	linux-kernel@...r.kernel.org, fuse-devel@...ts.sourceforge.net
Subject: Re: [PATCHSET] CUSE: implement CUSE, take #3

Miklos Szeredi wrote:
> On Thu, 30 Apr 2009, Tejun Heo wrote:
>> Tejun Heo wrote:
>>>> I'll post the updated libfuse patch as well.  Please let me know if
>>>> you find anything wrong with the current patches.
>>> Looks good to me.  Much prettier with two inits merged.
>> Oh... what happened to CUSE_INIT_DONE?
> 
> By moving the CUSE_INIT reply processing into the ->end() callback,
> the device initialization becomes synchronous with the process writing
> the message into the cuse device.
> 
> This means, that the process can simply wait for the write() on the
> device to complete before proceeding.
> 
> I've updated the libfuse patch so it calls ->init_done() after sending
> the CUSE_INIT reply.

Ah... cool.  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/