mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Laurent Riffard <laurent.riffard@free.fr>
Cc: petero2@telia.com, arjan@linux.intel.com, mingo@elte.hu,
	linux-kernel@vger.kernel.org, axboe@suse.de
Subject: Re: [patch] lockdep: annotate pktcdvd natural device hierarchy
Date: Mon, 24 Jul 2006 19:27:18 -0700	[thread overview]
Message-ID: <20060724192718.547a836e.akpm@osdl.org> (raw)
In-Reply-To: <44BA1609.9050305@free.fr>

On Sun, 16 Jul 2006 12:33:45 +0200
Laurent Riffard <laurent.riffard@free.fr> wrote:

> 
> Thank you Peter, the above patch removed the "possible recursive 
> locking detected" message. 
> 
> Now, I've got a new one (will this thread never end ?):
> 
> pktcdvd: writer pktcdvd0 mapped to hdc
> INFO: trying to register non-static key.
> the code is fine but needs lockdep annotation.
> turning off the locking correctness validator.
>  [<c0104db5>] show_trace+0xd/0x10
>  [<c0104dd1>] dump_stack+0x19/0x1c
>  [<c012c2e1>] __lock_acquire+0x10f/0x9a5
>  [<c012cbd7>] lock_acquire+0x60/0x80
>  [<c0292131>] _spin_lock_irq+0x1f/0x2e
>  [<c028fe86>] wait_for_completion+0x29/0xe5
>  [<e1136299>] pkt_generic_packet+0x1bb/0x1e8 [pktcdvd]
>  [<e113671a>] pkt_get_disc_info+0x3d/0x77 [pktcdvd]
>  [<e113836f>] pkt_open+0xc3/0xbf4 [pktcdvd]
>  [<c0159c36>] do_open+0xa1/0x3bd
>  [<c015a179>] blkdev_open+0x1f/0x48
>  [<c0151c87>] __dentry_open+0xb8/0x186
>  [<c0151dc3>] nameidata_to_filp+0x1c/0x2e
>  [<c0151e03>] do_filp_open+0x2e/0x35
>  [<c0152ce1>] do_sys_open+0x40/0xbb
>  [<c0152d88>] sys_open+0x16/0x18
>  [<c0102c2d>] sysenter_past_esp+0x56/0x8d

I assume this:

--- a/drivers/block/pktcdvd.c~pktcdvd-lockdep-fixes-fix
+++ a/drivers/block/pktcdvd.c
@@ -348,7 +348,7 @@ static int pkt_generic_packet(struct pkt
 	char sense[SCSI_SENSE_BUFFERSIZE];
 	request_queue_t *q;
 	struct request *rq;
-	DECLARE_COMPLETION(wait);
+	DECLARE_COMPLETION_ONSTACK(wait);
 	int err = 0;
 
 	q = bdev_get_queue(pd->bdev);
_

will shut that up.

Arjan, do we still need
lockdep-annotate-pktcdvd-natural-device-hierarchy.patch?

And could you please take a look at Peter's block_dev.c changes?  Closely,
please - it'd be nice to get this right one of these days ;)


  reply	other threads:[~2006-07-25  2:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-08 19:09 2.6.17-rc6-mm1/pktcdvd - BUG: possible circular locking Laurent Riffard
2006-06-12 15:14 ` Arjan van de Ven
2006-06-12 16:41   ` Jens Axboe
2006-06-21 10:21     ` Arjan van de Ven
2006-06-22 14:50   ` Peter Osterlund
2006-06-22 18:20     ` Arjan van de Ven
2006-07-14 11:22       ` Peter Osterlund
2006-07-14 13:46         ` Arjan van de Ven
2006-07-14 21:06           ` Peter Osterlund
2006-07-14 22:29             ` Arjan van de Ven
2006-07-15  7:04             ` [patch] lockdep: annotate pktcdvd natural device hierarchy Arjan van de Ven
2006-07-15 10:35               ` Laurent Riffard
2006-07-15 10:57                 ` Peter Osterlund
2006-07-16 10:33                   ` Laurent Riffard
2006-07-25  2:27                     ` Andrew Morton [this message]
2006-07-25  5:34                       ` Arjan van de Ven
2006-07-25  6:31                         ` Andrew Morton

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=20060724192718.547a836e.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=arjan@linux.intel.com \
    --cc=axboe@suse.de \
    --cc=laurent.riffard@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=petero2@telia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®