linux-kernel - Re: [PATCH 04/22][RFC] Unionfs: Common file 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: <1157256659.5637.12.camel@localhost>
Date:	Sun, 03 Sep 2006 00:10:59 -0400
From:	Trond Myklebust <trond.myklebust@....uio.no>
To:	Josef Sipek <jsipek@....cs.sunysb.edu>
Cc:	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	hch@...radead.org, akpm@...l.org, viro@....linux.org.uk
Subject: Re: [PATCH 04/22][RFC] Unionfs: Common file operations

On Fri, 2006-09-01 at 22:47 -0400, Josef Sipek wrote:

> From what I can see, the solution to this would be to pass the lookup
> intents in unionfs_lookup down to the lower filesystem (the way it should be
> done in the first place). Then, we could use the dentry here without any
> problems. Is that all that needs to be done or am I forgetting something?

That sounds correct. If you pass the lookup intents down to the
underlying filesystem while doing the lookup, then all should be well:
NFS will actually open the file for you at that point too, whereas most
other filesystems will just look it up and return the dentry.

In any case, you avoid the race, because you lookup/revalidate the
underlying dentry at the same time as you lookup/revalidate the unionfs
dentry.

Cheers,
  Trond


-- 
VGER BF report: H 0
-
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/