From: Jens Axboe <axboe@suse.de>
To: Srinivas Ganji <srinivasganji.linux@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Spinlock Related Debug Messages in Block Driver
Date: Tue, 11 Jul 2006 09:17:54 +0200 [thread overview]
Message-ID: <20060711071753.GS5210@suse.de> (raw)
In-Reply-To: <4dccc9070607102303v380281adp3943e1d58fad8d0@mail.gmail.com>
On Tue, Jul 11 2006, Srinivas Ganji wrote:
> Dear All,
>
> I implemented the sample block driver for the removable devices and
> the code contains no statements related to the spin lock except a lock
> to the blk_init_queue API as shown below.
>
> spinlock_t qlock;
> gDisk->blkqueue = blk_init_queue(do_my_request, &gDisk->qlock);
>
> The kernel version is 2.6.10.
>
> Everything works fine but when I try to copy a file of huge size
> (about 100MB), the following debug messages are getting displayed on
> the console:
>
> Fc3: drivers/block/ll_rw_blk.c: 2351: spin_lock already locked by the
> drivers.
> Fc3: drivers/block/ll_rw_blk.c: 2468: spin_unlock not locked by the drivers.
>
> In spite of these debug messages; the file is getting copied successfully.
> I studied the Block driver 16th chapter in LDD third edition.
>
> Can any one provide a pointer to these debug messages. Do I need to
> implement any patches for the kernel.
You need to initialize the lock passed to blk_init_queue() first. See eg
spin_lock_init(), or one of the static initializers
(SPIN_LOCK_UNLOCKED).
--
Jens Axboe
next prev parent reply other threads:[~2006-07-11 7:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-11 6:03 Spinlock Related Debug Messages in Block Driver Srinivas Ganji
2006-07-11 7:17 ` Jens Axboe [this message]
2006-07-11 7:42 ` Srinivas Ganji
2006-07-11 7:46 ` 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=20060711071753.GS5210@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivasganji.linux@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.