Re: [PATCH 00/22][RFC] Unionfs: Stackable Namespace Unification Filesystem

Hi!

> - Modifying a Unionfs branch directly, while the union is mounted, is
>   currently unsupported.  Any such change may cause Unionfs to oops and it
>   can even result in data loss!

I'm not sure if that is acceptable. Even root user should be unable to
oops the kernel using 'normal' actions.
						Pavel
-- 
Thanks for all the (sleeping) penguins.

-- 
VGER BF report: H 5.1371e-14
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [PATCH 00/22][RFC] Unionfs: Stackable Namespace Unification Filesystem
  - From: Shaya Potter <[email protected]>
- Re: [PATCH 00/22][RFC] Unionfs: Stackable Namespace Unification Filesystem
  - From: Jörn Engel <[email protected]>

References:
- [PATCH 00/22][RFC] Unionfs: Stackable Namespace Unification Filesystem
  - From: Josef Sipek <[email protected]>

Prev by Date: [PATCH] [MM] kerneldoc error on ata_piix.c
Next by Date: Re: Conversion to generic boolean
Previous by thread: [PATCH 21/22][RFC] Unionfs: Unlink
Next by thread: Re: [PATCH 00/22][RFC] Unionfs: Stackable Namespace Unification Filesystem
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]