Re: [patch 01/10] vfs: add path_create() and path_mknod()

[Erez Zadok]

In message <E1JhJwR-0008Vv-2x@xxxxxxxxxxxxxxxxxxx>, Miklos Szeredi writes:
[...]
> If it wants to handle that case nicely, it can monitor /proc/mounts
> and reflect it in it's superblock flags.  And it can take a write-ref
> on the underlying fs if it has outstanding dirtyness.  But we should
> not _rely_ on ecryptfs to ensure that it's never writing to a
> read-only mount.

I'm all for reducing the need for stackable f/s such as ecryptfs from having
to remember to manage the write counts.  A stackable filesystem has to
emulate some parts of the VFS when it calls into a lower f/s: in that case,
having useful VFS helpers that do as much of the work as possible, saves a
lot of hassle.

> Miklos

Cheers,
Erez.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/