linux-kernel - Re: [PATCH] hostfs: Use noop

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: <54B62C49.7030309@nod.at>
Date:	Wed, 14 Jan 2015 09:43:53 +0100
From:	Richard Weinberger <richard@....at>
To:	Christoph Hellwig <hch@...radead.org>
CC:	user-mode-linux-devel@...ts.sourceforge.net, dxld@...kboxed.org,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	stable@...r.kernel.org
Subject: Re: [PATCH] hostfs: Use noop_fsync for directories

Am 14.01.2015 um 09:39 schrieb Christoph Hellwig:
> On Tue, Jan 13, 2015 at 11:26:38PM +0100, Richard Weinberger wrote:
>> hostfs tries do reduce the amount of syscall between guest and host as much
>> as possible. For file operations it passes everything down to the host but
>> for directory operations only ->iterate() does.
>>
>> It is already horrible slow, if we add an ->open() for directory too it would
>> get even more slower. :-(
> 
> This sounds fairlt dangerous.  At least add some good documentation
> explaining these semantics.

Understood. Maybe it is time to rebenchmark hostfs with full directory pass-through support.
Daniel, are you interested in a small kernel project?
As explained on IRC adding real support for directory fsync() should be an easy task.
The only interesting point is how much overhead it will add.

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