From: Stefan.Bader@de.ibm.com
To: Jens Axboe <axboe@suse.de>
Cc: Alexander Viro <viro@math.psu.edu>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: loop.c: (rare) race condition
Date: Mon, 28 May 2001 09:59:08 +0200 [thread overview]
Message-ID: <C1256A5A.002BDE5F.00@d12mta05.de.ibm.com> (raw)
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.
reply other threads:[~2001-05-28 7:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C1256A5A.002BDE5F.00@d12mta05.de.ibm.com \
--to=stefan.bader@de.ibm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).