| From | Subject | Date |
|---|---|---|
| akpm | + embed-a-struct-path-into-struct-nameidata-instead-of-nd-de...
The patch titled
Embed a struct path into struct nameidata instead of nd->{dentry,mnt}
has been added to the -mm tree. Its filename is
embed-a-struct-path-into-struct-nameidata-instead-of-nd-dentrymnt-unionfs.patch
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
------------------------------------------------------
Subject: Embed a struct path into...
| Nov 5, 5:03 pm 2007 |
| akpm | + introduce-path_put.patch added to -mm tree
[Empty message]
| Nov 5, 5:02 pm 2007 |
| akpm | + embed-a-struct-path-into-struct-nameidata-instead-of-nd-de...
[Empty message]
| Nov 5, 5:01 pm 2007 |
| Jörn | Re: + embed-a-struct-path-into-struct-nameidata-instead-of-n...
Frowned-upon-by: Joern Engel <joern@logfs.org>
This patch changes some 400 lines, most if not all of which get longer
and more complicated to read. 23 get sufficiently longer to require an
additional linebreak. I can't remember complexity being invited into
the kernel without good reasoning, yet the patch description is
The following two patches manage to remove 7 lines in total. In total
23 were added, 7 removed , 400+ made longer and more complicated. Is
there another more favorable m...
| Nov 5, 6:10 pm 2007 |
| Evgeniy Polyakov | [3/4] Distributed storage. Algorithms.
Mirror and linear data stripping algorithms for DST.
Signed-off-by: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
diff --git a/drivers/block/dst/alg_linear.c b/drivers/block/dst/alg_linear.c
new file mode 100644
index 0000000..cb77b57
--- /dev/null
+++ b/drivers/block/dst/alg_linear.c
@@ -0,0 +1,104 @@
+/*
+ * 2007+ Copyright (c) Evgeniy Polyakov <johnpol@2ka.mipt.ru>
+ * All rights reserved.
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the ...
| Nov 5, 2:42 pm 2007 |
| Evgeniy Polyakov | [4/4] Distributed storage. Core interfaces.
This one contains core interfaces of the distributed storage, storage
and node initialization and cleanup code, block layer callbacks and the
like. It also contains Kconfig and Makefile changes.
Signed-off-by: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
diff --git a/drivers/block/Kconfig b/drivers/block/Kconfig
index b4c8319..ca6592d 100644
--- a/drivers/block/Kconfig
+++ b/drivers/block/Kconfig
@@ -451,6 +451,8 @@ config ATA_OVER_ETH
This driver provides Support for ATA over Ethernet block
...
| Nov 5, 2:42 pm 2007 |
| Evgeniy Polyakov | [2/4] Distributed storage. Network processing.
This file contains all bits needed for async non-blocking network
processing of the block requests directed to DST.
Signed-off-by: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
diff --git a/drivers/block/dst/kst.c b/drivers/block/dst/kst.c
new file mode 100644
index 0000000..ba5e5ef
--- /dev/null
+++ b/drivers/block/dst/kst.c
@@ -0,0 +1,1475 @@
+/*
+ * 2007+ Copyright (c) Evgeniy Polyakov <johnpol@2ka.mipt.ru>
+ * All rights reserved.
+ *
+ * This program is free software; you can redi...
| Nov 5, 2:42 pm 2007 |
| Evgeniy Polyakov | [1/4] Distributed storage. Documentation.
DST documentation.
Signed-off-by: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
diff --git a/Documentation/dst/algorithms.txt b/Documentation/dst/algorithms.txt
new file mode 100644
index 0000000..1437a6a
--- /dev/null
+++ b/Documentation/dst/algorithms.txt
@@ -0,0 +1,115 @@
+Each storage by itself is just a set of contiguous logical blocks, with
+allowed number of operations. Nodes, each of which has own start and size,
+are placed into storage by appropriate algorithm, which remaps
+logical ...
| Nov 5, 2:42 pm 2007 |
| Evgeniy Polyakov | [0/4] Distributed storage. Squizzed black-out of the dancing...
Hi.
I'm pleased to announce 7'th and the final release of the distributed
storage subsystem (DST). It allows to form a storage on top of local and
remote nodes and combine them in linear or mirroring setup, which in
turn can be exported to remote nodes.
Short changelog:
* added strong checksum support (Castagnoli crc)
* extended autoconfiguration (added ability to request if remote
side supports strong checksum and turn it on if needed)
* documentation addon - sysfs files
* added clean/dirty ...
| Nov 5, 2:41 pm 2007 |
| Chris Mason | 2008 Linux Storage and Filesystem Workshop
Hello everyone,
The position statement submission system for the 2008 storage and
filesystem workshop is now online. This is how you let us know you're
interested in attending and what topics are most important for
discussion.
For all the details, please see:
http://www.usenix.org/events/lsf08/
-chris
-
| Nov 5, 11:17 am 2007 |
| Phillip Lougher | [ANN] Squashfs 3.3 released
Hi,
I'm pleased to announce another release of Squashfs. This is the 22nd
release in just over five years. Squashfs 3.3 has lots of nice improvements,
both to the filesystem itself (bigger blocks and sparse files), but
also to the Squashfs-tools Mksquashfs and Unsquashfs.
The next stage after this release is to fix the one remaining blocking issue
(filesystem endianness), and then try to get Squashfs mainlined into the
Linux kernel again.
The list of changes from the change-log are as follow...
| Nov 5, 7:13 am 2007 |
| Michael Tokarev | Re: [ANN] Squashfs 3.3 released
Thanks Phillip.
A tiny bug[fix] I always forgot to send... In fs/squashfs/inode.c,
constants TASK_UNINTERRUPTIBLE and TASK_INTERRUPTIBLE are used, but
they aren't sometimes defined (declared in linux/sched.h):
CC [M] fs/squashfs/inode.o
fs/squashfs/inode.c: In function 'squashfs_get_cached_block':
fs/squashfs/inode.c:367: error: 'TASK_UNINTERRUPTIBLE' undeclared (first use in this function)
fs/squashfs/inode.c:367: error: (Each undeclared identifier is reported only once
fs/squashfs/inode....
| Nov 5, 7:19 pm 2007 |
| maximilian attems | Re: [ANN] Squashfs 3.3 released
that would be very cool!
with my hat as debian kernel maintainer i'd be very relieved to see it
mainlined. i don't know of any major distro that doesn't ship it.
thanks
--
maks
-
| Nov 5, 7:56 am 2007 |
| Tetsuo Handa | Is it illegal to refer namespace_sem while inode's mutex held?
Hello.
I'm running my LSM module on kernel 2.6.23 / Debian Sarge.
I encountered the following warning message.
It seems that calling down_read(&namespace_sem) is not permitted
inside mutex_lock(&inode->i_mutex) , but I'm not sure.
Is it illegal to refer namespace_sem while inode's mutex held?
=======================================================
[ INFO: possible circular locking dependency detected ]
2.6.23-tomoyo2.1 #27
-------------------------------------------------------...
| Nov 5, 6:59 am 2007 |
| Al Boldi | Massive slowdown when re-querying large nfs dir
There is a massive (3-18x) slowdown when re-querying a large nfs dir (2k+
entries) using a simple ls -l.
On 2.6.23 client and server running userland rpc.nfs.V2:
first try: time -p ls -l <2k+ entry dir> in ~2.5sec
more tries: time -p ls -l <2k+ entry dir> in ~8sec
first try: time -p ls -l <5k+ entry dir> in ~9sec
more tries: time -p ls -l <5k+ entry dir> in ~180sec
On 2.6.23 client and 2.4.31 server running userland rpc.nfs.V2:
first try: time -p ls -l <2k+ e...
| Nov 5, 12:58 am 2007 |
| David Chinner | Re: writeout stalls in current -git
Ok, so it's probably a side effect of the writeback changes.
Attached are two patches (two because one was in a separate patchset as
a standalone change) that should prevent async writeback from blocking
on locked inode cluster buffers. Apply the xfs-factor-inotobp patch first.
Can you see if this fixes the problem?
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
| Nov 4, 9:45 pm 2007 |
| Torsten Kaiser | Re: writeout stalls in current -git
Now testing v2.6.24-rc1-650-gb55d1b1+ the fix for the missapplied raid5-patch
Applying your two patches ontop of that does not fix the stalls.
vmstat 10 output from unmerging (uninstalling) a kernel:
1 0 0 3512188 332 192644 0 0 185 12 368 735 10 3 85 1
-> emerge starts to remove the kernel source files
3 0 0 3506624 332 192836 0 0 15 9825 2458 8307 7 12 81 0
0 0 0 3507212 332 192836 0 0 0 554 630 1233 0 1 99 0
0 0 ...
| Nov 5, 2:27 pm 2007 |
| Torsten Kaiser | Re: writeout stalls in current -git
Applied both patches against the kernel mentioned above.
This blows up at boot:
[ 80.807589] Filesystem "dm-0": Disabling barriers, not supported by
the underlying device
[ 80.820241] XFS mounting filesystem dm-0
[ 80.913144] ------------[ cut here ]------------
[ 80.914932] kernel BUG at drivers/md/raid5.c:143!
[ 80.916751] invalid opcode: 0000 [1] SMP
[ 80.918338] CPU 3
[ 80.919142] Modules linked in:
[ 80.920345] Pid: 974, comm: md1_raid5 Not tainted 2.6.24-rc1 #3
[ 80.9226...
| Nov 5, 3:01 am 2007 |
| Andrew Morton | Re: writeout stalls in current -git
On Fri, 2 Nov 2007 18:33:29 +0800
Given the problems we're having in there I'm a bit reluctant to go tossing
hastily put together and inadequately tested stuff onto the fire. And
that's what this patch looks like to me.
Wanna convince me otherwise?
-
| Nov 5, 7:57 pm 2007 |
| Mel Gorman | Re: migratepage failures on reiserfs
The grow_dev_page() pages should be reclaimable even though migration
is not supported for those pages? They were marked movable as it was
useful for lumpy reclaim taking back pages for hugepage allocations and
the like. Would it make sense for memory unremove to attempt migration
first and reclaim second?
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
-
| Nov 5, 6:23 am 2007 |
| Christoph Lameter | Re: migratepage failures on reiserfs
Note that a page is still movable even if there is no file system method
for migration available. In that case the page needs to be cleaned before
it can be moved.
-
| Nov 5, 6:46 pm 2007 |
| Chris Mason | Re: migratepage failures on reiserfs
On Mon, 5 Nov 2007 10:23:35 +0000
In this case, reiserfs has the page pinned while it is doing journal
magic. Not sure if ext3 has the same issues.
-chris
-
| Nov 5, 9:40 am 2007 |
| Hugh Dickins | Re: msync(2) bug(?), returns AOP_WRITEPAGE_ACTIVATE to userl...
[Dave, I've Cc'ed you re handle_write_count_underflow, see below.]
That's good news, and that unionfs_writepage looks good to me -
with three reservations I've not observed before.
One, I think you would be safer to do a set_page_dirty(lower_page)
before your clear_page_dirty_for_io(lower_page). I know that sounds
silly, but see Linus' "Yes, Virginia" comment in clear_page_dirty_for_io:
there's a lot of subtlety hereabouts, and I think you'd be mimicing the
usual path closer if you set_page_di...
| Nov 5, 11:40 am 2007 |
| Dave Hansen | Re: msync(2) bug(?), returns AOP_WRITEPAGE_ACTIVATE to userl...
I've never actually seen this happen in practice, but I do know exactly
Actually, I think your s/while/if/ change is probably a decent fix.
Barring any other races, that loop should always have made progress on
and don't have a positive mnt->__mnt_writers, we know something is going
badly. We WARN_ON() there, which should at least give an earlier
warning that the system is not doing well. But it doesn't fix the
inevitable. Could you try the attached patch and see if it at least
warns you ...
| Nov 5, 12:38 pm 2007 |
| Hugh Dickins | Re: msync(2) bug(?), returns AOP_WRITEPAGE_ACTIVATE to userl...
Thanks, Dave, yes, that gives me a nice warning:
leak detected on mount(c25ebd80) writers count: -65537
WARNING: at fs/namespace.c:249 handle_write_count_underflow()
[<c0103486>] show_trace_log_lvl+0x1b/0x2e
[<c01034b6>] show_trace+0x16/0x1b
[<c0103589>] dump_stack+0x19/0x1e
[<c0171906>] handle_write_count_underflow+0x4c/0x60
[<c0171983>] mnt_drop_write+0x69/0x8e
[<c0160211>] __fput+0xff/0x162
[<c016010d>] fput+0x2e/0x33
[<c01b8f63>] un...
| Nov 5, 2:57 pm 2007 |
| previous day | today | next day |
|---|---|---|
| November 4, 2007 | November 5, 2007 | November 6, 2007 |
