From: "Thomas S. Iversen" <zensonic@zensonic.dk>
To: device-mapper development <dm-devel@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Help tracking down problem --- endless loop in __find_get_block_slow
Date: Mon, 21 Feb 2005 11:46:50 +0100 [thread overview]
Message-ID: <4219BC1A.1060007@zensonic.dk> (raw)
Hi There
I am trying to develop a device mapper plugin which does transparent
block encryption and sector shuffling in the style freebsd does it (GBDE)
Reads are support and working, but have trouble getting writes to work
properly.
If I do a simple:
echo "test" > /mnt/test (where /mnt is /dev/mapper/gbde)
sync
it works just fine. If I do
dd if=/dev/zero of=/mnt/testfile count=N, N=1..6 it works fine
But if I do
dd if=/dev/zero of=/mnt/testfile count=N, N>6
I get into an endless loop in __find_get_block_slow. My write path does
something like this:
recieve original BIO (eg. size=4096). Split BIO into sectorsize chunks.
map chunks to physical sectors.
encrypt sectors
generate keys
write sectors
update keysectors
... when all sectors are written call bio_endio on the original request.
To awoid allocating alot of pages during writes, I use the mem from the
original request to do encryption "inplace". Could that be the cause of
my problems? I would clearly like to minimize the need for page
allocation in my dm-module, so I hope it isn't.
Whats going on here? Every comments appriciated!
Regards Thomas
next reply other threads:[~2005-02-21 10:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 10:46 Thomas S. Iversen [this message]
2005-02-22 9:18 ` Help tracking down problem --- endless loop in __find_get_block_slow Andrew Morton
2005-02-22 22:46 ` Jeff Mahoney
2005-02-22 23:28 ` Andrew Morton
2005-02-26 0:03 ` Jeff Mahoney
2005-02-28 21:06 ` Jeff Mahoney
2005-02-28 21:09 ` Help tracking down problem --- endless loop in __find_get_block_slow (now with the patch) Jeff Mahoney
2005-02-23 12:00 ` Help tracking down problem --- endless loop in __find_get_block_slow Thomas S. Iversen
2005-02-23 12:10 ` Andrew Morton
2005-02-23 13:02 ` Thomas S. Iversen
2005-02-23 20:09 ` Andrew Morton
2005-02-23 22:24 ` Thomas S. Iversen
2005-02-23 23:17 ` Andrew Morton
2005-02-24 8:54 ` Thomas S. Iversen
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=4219BC1A.1060007@zensonic.dk \
--to=zensonic@zensonic.dk \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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