From: Michael Zhu <mylinuxk@yahoo.ca>
To: linux-kernel@vger.kernel.org
Subject: About the request queue of block device
Date: Mon, 7 Jan 2002 16:37:49 -0500 (EST) [thread overview]
Message-ID: <20020107213749.18573.qmail@web14911.mail.yahoo.com> (raw)
Hello, everyone, I have a question about the request
queue of block device.
I intercept the request function of floppy disk device
by changing the pointer,
"blk_dev[2].request_queue.request_fn", in my kernel
module. The following is the source code.
original_request_fn_proc =
blk_dev[2].request_queue.request_fn;
blk_dev[2].request_queue.request_fn =
my_request_fn_proc;
In my own my_request_fn_proc() I use the "req =
blkdev_entry_next_request(&rq->queue_head)" function
to get the pointer of the request structure. When
req->cmd is WRITE I encrypt all the b_data buffer of
the buffer header. Then I call the
original_request_fn_proc(). And it works. The data on
the floppy disk is some kind of cipher data. The
trouble is when the req->cmd is READ. I don't know
whether the b_data buffer contains the data read from
the floppy disk after I call the
original_request_fn_proc() function. When read a block
from the block device, where is the data is placed?
In my module I use the blkdev_next_request() function
to get the next request. When I want to do the same
thing to this next request, the Linux kernel
deadlocked. I must reboot the OS. What is wrong?
Any idea will be appreciated. Thanks in advance.
Michael
______________________________________________________
Send your holiday cheer with http://greetings.yahoo.ca
next reply other threads:[~2002-01-07 21:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-07 21:37 Michael Zhu [this message]
2002-01-08 7:15 ` Jens Axboe
2002-01-09 7:36 ` Michael Zhu
2002-01-09 14:28 ` Jens Axboe
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=20020107213749.18573.qmail@web14911.mail.yahoo.com \
--to=mylinuxk@yahoo.ca \
--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
Powered by JetHome