linux-kernel - Re: [RFC] Union Mount: Readdir approaches

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: <Pine.LNX.4.64.0709071637180.25942@fbirervta.pbzchgretzou.qr>
Date:	Fri, 7 Sep 2007 16:39:08 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Bharata B Rao <bharata@...ux.vnet.ibm.com>
cc:	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	hch@...radead.org, Jan Blunck <jblunck@...e.de>,
	Josef 'Jeff' Sipek <jsipek@...sunysb.edu>
Subject: Re: [RFC] Union Mount: Readdir approaches

On Sep 7 2007 11:16, Bharata B Rao wrote:

>Questions
>---------
>The main problem in getting a sane readdir() implementation in Union Mount
>is the fact that a single vfs object (file structure) is used to represent
>more than one (underlying) directory. Because of this, it is unclear as to
>how lseek(2) needs to behave in such cases.
>
>First of all, should we even expect a sane lseek(2) on union mounted
>directories ? If not, will the Approach 2, which works uniformly for
>all filesystem types be acceptable ?

Filesystems also have this problem. http://lkml.org/lkml/2007/4/7/107
If you ask me, we should entriely do away with the telldir/seekdir
blackmagic (and add appropriate compat code).



	Jan
-- 
-
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/