| 170128574231_502860007886 | Jan Blunck |
|
I think it is wrong to unconditionally take the lock before calling
atomic_dec_and_test() in _atomic_dec_and_lock(). This will deadlock in
situation where it is known that the counter will now reach |
|
| |
| 189029194580_579560007145 | Jan Blunck |
|
Creates the proper struct union_mount when mounting something into a
union. If the topmost filesystem isnt capable of handling the white-out
filetype it could only be mount read-only.
Signed-off-by: |
|
| |
| 188726354272_580360007915 | Jan Blunck |
|
From: Valerie Aurora (Henson) <vaurora@xxxxxxxxxx
Add support for fallthru entries to tmpfs.
Signed-off-by: Valerie Aurora (Henson) <vaurora@xxxxxxxxxx
---
fs/dcache.c | 4 ++-
fs/libfs |
|
| |
| 116225834207_557460007173 | Jan Blunck |
|
Honor the S_OPAQUE flag in the union path lookup.
Signed-off-by: Jan Blunck <jblunck@xxxxxxx
Signed-off-by: Valerie Aurora (Henson) <vaurora@xxxxxxxxxx
---
fs/namei.c | 17 ++++++++++++++- |
|
| |
| 192224744668_528960007814 | Jan Blunck |
|
Add per mountpoint flag for Union Mount support. You need additional patches
to util-linux for that to work - see:
git://git.kernel.org/pub/scm/utils/util-linux-ng/val/util-linux-ng.git
Signed-off- |
|
| |
| 199423764670_522460007255 | Jan Blunck |
|
This patch changes real_lookup() into returning a struct path.
Signed-off-by: Jan Blunck <jblunck@xxxxxxx
Signed-off-by: Valerie Aurora (Henson) <vaurora@xxxxxxxxxx
---
fs/namei.c | 82 ++ |
|
| |
| 110922954173_569060007889 | Jan Blunck |
|
Simply white-out a given directory entry. This functionality is usually used
in the sense of unlink. Therefore the given dentry can still be in-use and
contains an in-use inode. The filesystems inode |
|
| |
| 183529774523_510760007983 | Jan Blunck |
|
Add some additional checks when mounting something into an union.
Signed-off-by: Jan Blunck <jblunck@xxxxxxx
Signed-off-by: Miklos Szeredi <mszeredi@xxxxxxx
Signed-off-by: Valerie Aurora (He |
|
| |
| 102129424566_522960007196 | Jan Blunck |
|
From: Valerie Aurora (Henson) <vaurora@xxxxxxxxxx
Define the fallthru dcache flag and file system op.
Signed-off-by: Valerie Aurora (Henson) <vaurora@xxxxxxxxxx
---
include/linux/dcache.h |
|
| |
| 140224364670_506960007345 | Jan Blunck |
|
From: Valerie Aurora (Henson) <vaurora@xxxxxxxxxx
Define the fallthru dcache flag and file system op.
Signed-off-by: Valerie Aurora (Henson) <vaurora@xxxxxxxxxx
---
include/linux/dcache.h |
|
| |
| 188327194722_555360007126 | Jan Blunck |
|
This patch adds support for whiteouts to tmpfs.
Signed-off-by: Jan Blunck <jblunck@xxxxxxx
Signed-off-by: David Woodhouse <dwmw2@xxxxxxxxxxxxx
Signed-off-by: Valerie Aurora (Henson) <vaur |
|
| |
| 180920524421_598260007511 | Jan Blunck |
|
This patch adds support for whiteouts to tmpfs.
Signed-off-by: Jan Blunck <jblunck@xxxxxxx
Signed-off-by: David Woodhouse <dwmw2@xxxxxxxxxxxxx
Signed-off-by: Valerie Aurora (Henson) <vaur |
|
| |
| 187125774487_539360007265 | Jan Blunck |
|
The userspace isnt ready for handling another filetype. Therefore this
patch lets readdir() and others skip over the whiteout directory entries
they might find.
Signed-off-by: Jan Blunck <j.blunc |
|
| |
| 137527064206_594260007721 | Jan Blunck |
|
The userspace isnt ready for handling another filetype. Therefore this
patch lets readdir() and others skip over the whiteout directory entries
they might find.
Signed-off-by: Jan Blunck <j.blunc |
|
| |
| 113723374157_580860007884 | Jan Blunck |
|
Break early when somebody tries to rehash an already hashed dentry.
Otherwise this leads to interesting corruptions in the dcache hash table
later on.
Signed-off-by: Jan Blunck <jblunck@xxxxxxx
|
|
| |
| 115222894603_587560007546 | Jan Blunck |
|
Break early when somebody tries to rehash an already hashed dentry.
Otherwise this leads to interesting corruptions in the dcache hash table
later on.
Signed-off-by: Jan Blunck <jblunck@xxxxxxx
|
|
| |
| 100026514599_542260007341 | Arnd Bergmann |
|
Jan Blunck:
+Rename across different levels of the union is implemented as a copy-up
+operation for regular files. Rename of directories simply returns EXDEV, the
+same as if we tried to renam |
|
| |
| 193325024918_542060007602 | Arnd Bergmann |
|
Jan Blunck:
+Rename across different levels of the union is implemented as a copy-up
+operation for regular files. Rename of directories simply returns EXDEV, the
+same as if we tried to renam |
|
| |
| 168522714308_589260007242 | Valerie Aurora |
|
Arnd Bergmann:
Right, but that is consistent with how the kernel would treat a
rename from one mount point to another, and tools like mv
can handle this in user space.
Yes, that is the descri |
|
| |
| 161323504579_577160007986 | Valerie Aurora |
|
Arnd Bergmann:
Right, but that is consistent with how the kernel would treat a
rename from one mount point to another, and tools like mv
can handle this in user space.
Yes, that is the descri |
|
| |
| 165423104274_525660007116 | Valerie Aurora |
|
Valerie Aurora:
Ah, we did implement that in an earlier version. I dont know if we
dropped the patch by accident or on purpose, but the original version
is below. We will either put this fea |
|
| |
| 180321854768_540160007399 | Valerie Aurora |
|
Valerie Aurora:
Ah, we did implement that in an earlier version. I dont know if we
dropped the patch by accident or on purpose, but the original version
is below. We will either put this fea |
|
| |
| 174225404902_566060007797 | Valerie Aurora |
|
On May 18, 2009 16:40 -0400, Valerie Aurora wrote:
@@ -705,8 +707,9 @@ struct ext2_dir_entry_2 {
#define EXT2_FT_FIFO 5
#define EXT2_FT_SOCK 6
#define EXT2_FT_SYMLINK 7
+#define EXT2 |
|
| |
| 126226454068_557060007280 | Valerie Aurora |
|
On May 18, 2009 16:40 -0400, Valerie Aurora wrote:
@@ -705,8 +707,9 @@ struct ext2_dir_entry_2 {
#define EXT2_FT_FIFO 5
#define EXT2_FT_SOCK 6
#define EXT2_FT_SYMLINK 7
+#define EXT2 |
|
| |
| 181321484631_539260007788 | Jan Blunck |
|
On Mon, 18 May 2009, Jan Blunck wrote:
Here is another post of the VFS based union mount implementation.
Traditionally the mount operation is opaque, which means that the content of
the moun |
|
| |
| 137825734097_565360007281 | Jan Blunck |
|
On Mon, 18 May 2009, Jan Blunck wrote:
Here is another post of the VFS based union mount implementation.
Traditionally the mount operation is opaque, which means that the content of
the moun |
|
| |
| 176926324466_553660007073 | Jan Blunck |
|
On Tue, 19 May 2009, Jan Blunck wrote:
The directory in the topmost filesystem is created during
lookup. The contents of the directory isnt copied up presistently
at that point in time. Therefo |
|
| |
| 193627764614_583860007573 | Jan Blunck |
|
On Tue, 19 May 2009, Jan Blunck wrote:
The directory in the topmost filesystem is created during
lookup. The contents of the directory isnt copied up presistently
at that point in time. Therefo |
|
| |
| 163526984217_570360007754 | Jan Blunck |
|
On Tuesday 19 May 2009, Jan Blunck wrote:
So this means that the topmost branch always needs to be writable,
right? It isnt possible to make a union of two iso9660 filesystems,
for |
|
| |
| 198420804903_561460007821 | Jan Blunck |
|
On Tuesday 19 May 2009, Jan Blunck wrote:
So this means that the topmost branch always needs to be writable,
right? It isnt possible to make a union of two iso9660 filesystems,
for |
|
| |
| 140128504394_549960007223 | Jan Blunck |
|
On Tuesday 19 May 2009, Jan Blunck wrote:
On Tue, May 19, Arnd Bergmann wrote:
This would work, but youd have to do this for each file system if you want
to be able to use it as the top of |
|
| |
| 178022714856_524660007889 | Miklos Szeredi |
|
On Tue, May 19, 2009 at 11:48:00AM +0200, Miklos Szeredi wrote:
On Mon, 18 May 2009, Jan Blunck wrote:
Here is another post of the VFS based union mount implementation.
Traditionally t |
|
| |
| 132027444665_593460007099 | Miklos Szeredi |
|
On Wed, May 20, 2009 at 11:05:27AM +0200, Miklos Szeredi wrote:
On Tue, 19 May 2009, Valerie Aurora wrote:
As Jan said, readdir() of read-only unioned file systems works with a
tmpfs top la |
|
| |
| 150722154797_572560007064 | Jan Blunck |
|
On Tuesday 19 May 2009, Jan Blunck wrote:
On Tue, May 19, Arnd Bergmann wrote:
This would work, but youd have to do this for each file system if you want
to be able to use it as the top of |
|
| |
| 147829034144_538160007617 | Valerie Aurora |
|
On Mon, 18 May 2009, Jan Blunck wrote:
Here is another post of the VFS based union mount implementation.
Is there any chance this will support NFS? I can union-mount tmpfs over
nfs mounted fs, bu |
|
| |
| 120129184466_559660007969 | Miklos Szeredi |
|
On Tue, May 19, 2009 at 11:48:00AM +0200, Miklos Szeredi wrote:
On Mon, 18 May 2009, Jan Blunck wrote:
Here is another post of the VFS based union mount implementation.
Traditionally t |
|
| |
| 181921964240_567560007047 | Valerie Aurora |
|
On Mon, 08 Jun 2009, Valerie Aurora wrote:
On Thu, May 21, 2009 at 02:54:19PM +0200, Jan Rekorajski wrote:
On Mon, 18 May 2009, Jan Blunck wrote:
Here is another post of the VFS bas |
|
| |
| 156427644792_522860007372 | Miklos Szeredi |
|
On Wed, May 20, 2009 at 11:05:27AM +0200, Miklos Szeredi wrote:
On Tue, 19 May 2009, Valerie Aurora wrote:
As Jan said, readdir() of read-only unioned file systems works with a
tmpfs top la |
|
| |
| 132822044588_512560007507 | Valerie Aurora |
|
On Mon, 18 May 2009, Jan Blunck wrote:
Here is another post of the VFS based union mount implementation.
Is there any chance this will support NFS? I can union-mount tmpfs over
nfs mounted fs, bu |
|
| |
| 118924084409_533460007926 | Valerie Aurora |
|
On Mon, 08 Jun 2009, Valerie Aurora wrote:
On Tue, Jun 09, 2009 at 12:44:06AM +0200, Jan Rekorajski wrote:
On Mon, 08 Jun 2009, Valerie Aurora wrote:
Youll get -EBUSY on the second |
|
| |
| 195129914843_541760007258 | Valerie Aurora |
|
On Mon, 08 Jun 2009, Valerie Aurora wrote:
On Thu, May 21, 2009 at 02:54:19PM +0200, Jan Rekorajski wrote:
On Mon, 18 May 2009, Jan Blunck wrote:
Here is another post of the VFS bas |
|
| |
| 138624054455_562660007899 | Valerie Aurora |
|
On Mon, 2009-05-18 at 18:08 +0200, Jan Blunck wrote:
Here is another post of the VFS based union mount implementation.
Awesome work, this may just get us out of a tight spot with our LiveCD.
A |
|
| |
| 167326434662_546560007359 | Valerie Aurora |
|
On Mon, 08 Jun 2009, Valerie Aurora wrote:
On Tue, Jun 09, 2009 at 12:44:06AM +0200, Jan Rekorajski wrote:
On Mon, 08 Jun 2009, Valerie Aurora wrote:
Youll get -EBUSY on the second |
|
| |
| 183721994563_542560007493 | Jens Axboe |
|
Hi,
This is the fourth version of this patchset. Chances since v3:
- Dropped a prep patch, it has been included in mainline since.
- Add a work-to-do list to the bdi. This is struct bdi_work. Each |
|
| |
| 193225144901_534160007689 | Jens Axboe |
|
btrfs puts dirty inodes on there, so it must register a thread
to handle them. Also fixes failure to check bdi_init() return value,
and bad inherit of - capabilities flags from the default bdi.
Sign |
|
| |
| 126627994679_510860007264 | Valerie Aurora |
|
On Mon, 2009-05-18 at 18:08 +0200, Jan Blunck wrote:
Here is another post of the VFS based union mount implementation.
Awesome work, this may just get us out of a tight spot with our LiveCD.
A |
|
| |
| 136726014670_582360007749 | Jens Axboe |
|
Also a debugging aid. We want to catch dirty inodes being added to
backing devices that dont do writeback.
Signed-off-by: Jens Axboe <jens.axboe@xxxxxxxxxx
---
fs/fs-writeback.c | |
|
| |
| 172129004392_538260007264 | Jens Axboe |
|
Hi,
This is the fourth version of this patchset. Chances since v3:
- Dropped a prep patch, it has been included in mainline since.
- Add a work-to-do list to the bdi. This is struct bdi_work. Each |
|
| |
| 174122014463_530460007788 | Jens Axboe |
|
Not meant for inclusion, just to monitor what is going on while testing
this stuff.
Signed-off-by: Jens Axboe <jens.axboe@xxxxxxxxxx
---
mm/backing-dev.c | 43 ++++++++++++++++++++++++++++++++ |
|
| |
| 179825594301_569860007149 | Jens Axboe |
|
btrfs puts dirty inodes on there, so it must register a thread
to handle them. Also fixes failure to check bdi_init() return value,
and bad inherit of - capabilities flags from the default bdi.
Sign |
|
| |
