Hi,
I think I've stumbled over a rare case where the way the loop device now
handles loopback to files.
What I did: for the things I want to test I need block devices that end up
using the same physical
storage. So I use losetup to connect 2 (or more) loop devices to the same
file an then go on working
with these block devices. This worked with kernel 2.4.0 (plus loop6.patch)
without problems. But now
(kernel 2.4.4) I got kernel-bug (in UnlockPage while doing the end_io
call).
It seems that the loop device driver changed the way it accesses files to
use the page cache. So
I compared the function lo_send() in loop.c with the generic_file_write()
in mm/filemap.c. In that function
writings are serialized using the i_sem semaphore. So I added taht to
lo_send and after that my setup
worked again. It seem that since each loop device has its own kernel
thread doing the read/writes it was
possible that both tried to update the same _page_ at the same time
(although I made sure that I never
write the same _sector_ at the same time).
I don't know whether that is the best solution to the problem but at least
it works. :) Maybe it also helps in
other situations I haven't thought of, too. Hopefully the patch below
survives our mailing system...
Stefan
--- linux-2.4.4/drivers/block/loop.c Wed May 9 15:19:51 2001
+++ new/drivers/block/loop.c Wed May 23 15:18:48 2001
@@ -176,6 +176,8 @@
unsigned size, offset;
int len;
+ down(&(file->f_dentry->d_inode->i_sem));
+
index = pos >> PAGE_CACHE_SHIFT;
offset = pos & (PAGE_CACHE_SIZE - 1);
len = bh->b_size;
@@ -206,6 +208,7 @@
deactivate_page(page);
page_cache_release(page);
}
+ up(&(file->f_dentry->d_inode->i_sem));
return 0;
write_fail:
@@ -217,6 +220,7 @@
deactivate_page(page);
page_cache_release(page);
fail:
+ up(&(file->f_dentry->d_inode->i_sem));
return -1;
}
----------------------------------------------------------------------------------
When all other means of communication fail, try words.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu May 31 2001 - 21:00:35 EST