linux-kernel - Re: [patch 6/9] fuse: add export 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: <E1JvprY-0000S0-5v@pomaz-ex.szeredi.hu>
Date:	Tue, 13 May 2008 10:27:56 +0200
From:	Miklos Szeredi <miklos@...redi.hu>
To:	ezk@...sunysb.edu
CC:	hch@...radead.org, miklos@...redi.hu, akpm@...ux-foundation.org,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [patch 6/9] fuse: add export operations

> > Only finding in-memory inodes for nfs export is quite dangerous.  I
> > think it would be a much better idea to support whatever upcalls are
> > needed to find the object if it's not in memory.  Without that the nfs
> > exporting support is hardly useable.
> 
> In the ODF version of unionfs, we store the inode numbers persistently in a
> small /odf partition, exactly for that reason.

What do inode numbers index on that partition?  A path?  How do you
garbage collect unused inode numbers?

>  It'd be wonderful if there
> was kernel support for persistent inode numbers that could be used by
> various virtual filesystems.

Well, fuse for one doesn't need it because it's typically a function
that is best pushed to userspace.

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/