linux-kernel - Re: [PATCH 01/24] Unionfs: Documentation

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: <1168307442.5024.6.camel@localhost.localdomain>
Date:	Mon, 08 Jan 2007 20:50:42 -0500
From:	Shaya Potter <spotter@...columbia.edu>
To:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
Cc:	Josef Sipek <jsipek@....cs.sunysb.edu>,
	Giuseppe Bilotta <bilotta78@...pop.com>,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH 01/24] Unionfs: Documentation

On Tue, 2007-01-09 at 02:26 +0100, Jan Engelhardt wrote:
> On Jan 8 2007 19:33, Josef Sipek wrote:
> >On Tue, Jan 09, 2007 at 01:19:48AM +0100, Giuseppe Bilotta wrote:
> >> As a simple user without much knowledge of kernel internals, much less
> >> so filesystems, couldn't something based on the same principle of
> >> lsof+fam be used to handle these situations?
> >
> >Using inotify has been suggested before. That let the upper filesystem
> >know when something changed on the lower filesystem.
> >
> >I think that, while it would work, it is not the right solution.
> 
> Because inotify is not recursive yet?

Even if it was, using inotify would be inherently racy (what if two
writes start at the same time)

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