<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#ffffff" text="#000000">
    <tt>On 12/08/2011 07:47 AM, Srivatsa Bhat wrote:</tt>
    <blockquote
cite="mid:CAC_BnSVZeYO-nwzcLmQUMg=pVeuq+Lq8yEu3+Bzm3Lv0QxiGpA@mail.gmail.com"
      type="cite">
      <div class="gmail_quote">
        <div><tt>2 things:</tt></div>
        <div><tt>1. Documentation/lockdep-design.txt explains the
            "cryptic lock state symbols".</tt></div>
        <div><tt>2. Please post the lockdep splat _exactly_ as it
            appears, and _in full_&nbsp;</tt></div>
        <div><tt>&nbsp; &nbsp; (and without line-wrapping, if possible).&nbsp;Usually
            lockdep is intelligent</tt></div>
        <div><tt>&nbsp; &nbsp; enough to&nbsp;tell you the possible scenario that would
            lock up your system.</tt></div>
        <div><tt>&nbsp; &nbsp; That gives a very&nbsp;good clue,&nbsp;in case you find it
            difficult to make out what</tt></div>
        <div><tt>&nbsp; &nbsp; &nbsp;is wrong from the cryptic symbols.</tt></div>
        <div><tt><br>
          </tt></div>
        <div><tt>Regards,</tt></div>
        <div><tt>Srivatsa S. Bhat</tt></div>
      </div>
      <tt><br>
        <br>
      </tt>
      <tt><br>
      </tt>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <tt><br>
        _______________________________________________<br>
        Kernelnewbies mailing list<br>
        <a class="moz-txt-link-abbreviated" href="mailto:Kernelnewbies@kernelnewbies.org">Kernelnewbies@kernelnewbies.org</a><br>
        <a class="moz-txt-link-freetext" href="http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies">http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies</a><br>
      </tt></blockquote>
    <tt><br>
      Oh, sorry. I suppose I only included things that made any sense to
      me. If I were to hazard a guess after reading through the design
      doc, it sounds like there's a problem with the context in which
      locks are being acquired? That seems odd to me, since I don't get
      the inconsistent lock state until I'm trying to spin_unlock </tt><tt>&amp;sblsnap_snapshot_table[i].sblsnap_lock
      (which is why I assume it's listed as one that's currently held.</tt><br>
    <tt><br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel:
      =================================<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: [ INFO: inconsistent lock
      state ]<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: 2.6.32-220.el6.x86_64.debug #1<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel:
      ---------------------------------<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: inconsistent {IN-HARDIRQ-W}
      -&gt; {HARDIRQ-ON-W} usage.<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: tee/1966
      [HC0[0]:SC0[0]:HE1:SE1] takes:<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: (&amp;vblk-&gt;lock){?.-...},
      at: [&lt;ffffffffa04c4d2a&gt;] sblsnap_snap_now+0x25a/0x2a0
      [sblsnap]<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: {IN-HARDIRQ-W} state was
      registered at:<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel:&nbsp; [&lt;ffffffff810afbca&gt;]
      __lock_acquire+0x77a/0x1570<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel:&nbsp; [&lt;ffffffff810b0a64&gt;]
      lock_acquire+0xa4/0x120<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel:&nbsp; [&lt;ffffffff81520c75&gt;]
      _spin_lock_irqsave+0x55/0xa0<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel:&nbsp; [&lt;ffffffffa006b19b&gt;]
      blk_done+0x2b/0x110 [virtio_blk]<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel:&nbsp; [&lt;ffffffffa00401dc&gt;]
      vring_interrupt+0x3c/0xd0 [virtio_ring]<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel:&nbsp; [&lt;ffffffff810ec080&gt;]
      handle_IRQ_event+0x50/0x160<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel:&nbsp; [&lt;ffffffff810ee840&gt;]
      handle_edge_irq+0xe0/0x170<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel:&nbsp; [&lt;ffffffff8100e059&gt;]
      handle_irq+0x49/0xa0<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel:&nbsp; [&lt;ffffffff81526cdc&gt;]
      do_IRQ+0x6c/0xf0<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel:&nbsp; [&lt;ffffffff8100ba93&gt;]
      ret_from_intr+0x0/0x16<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel:&nbsp; [&lt;ffffffff810148e2&gt;]
      default_idle+0x52/0xc0<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel:&nbsp; [&lt;ffffffff81009e0b&gt;]
      cpu_idle+0xbb/0x110<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel:&nbsp; [&lt;ffffffff81516623&gt;]
      start_secondary+0x211/0x254<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: irq event stamp: 4699<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: hardirqs last&nbsp; enabled at
      (4699): [&lt;ffffffff81179e81&gt;] __kmalloc+0x241/0x330<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: hardirqs last disabled at
      (4698): [&lt;ffffffff81179d60&gt;] __kmalloc+0x120/0x330<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: softirqs last&nbsp; enabled at
      (4696): [&lt;ffffffff81076baa&gt;] __do_softirq+0x14a/0x200<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: softirqs last disabled at
      (4681): [&lt;ffffffff8100c30c&gt;] call_softirq+0x1c/0x30<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel:<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: other info that might help us
      debug this:<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: 1 lock held by tee/1966:<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: #0:&nbsp;
      (&amp;sblsnap_snapshot_table[i].sblsnap_lock){+.+.+.}, at:
      [&lt;ffffffffa04c4b7c&gt;] sblsnap_snap_now+0xac/0x2a0 [sblsnap]<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel:<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: stack backtrace:<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: Pid: 1966, comm: tee Not
      tainted 2.6.32-220.el6.x86_64.debug #1<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: Call Trace:<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: [&lt;ffffffff810ad947&gt;] ?
      print_usage_bug+0x177/0x180<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: [&lt;ffffffff810ae8ed&gt;] ?
      mark_lock+0x35d/0x430<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: [&lt;ffffffff810afa59&gt;] ?
      __lock_acquire+0x609/0x1570<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: [&lt;ffffffff810ab31d&gt;] ?
      trace_hardirqs_off+0xd/0x10<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: [&lt;ffffffff815208e7&gt;] ?
      _spin_unlock_irqrestore+0x67/0x80<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: [&lt;ffffffff8106ec43&gt;] ?
      release_console_sem+0x203/0x250<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: [&lt;ffffffff810b0a64&gt;] ?
      lock_acquire+0xa4/0x120<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: [&lt;ffffffffa04c4d2a&gt;] ?
      sblsnap_snap_now+0x25a/0x2a0 [sblsnap]<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: [&lt;ffffffff81520af6&gt;] ?
      _spin_lock+0x36/0x70<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: [&lt;ffffffffa04c4d2a&gt;] ?
      sblsnap_snap_now+0x25a/0x2a0 [sblsnap]<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: [&lt;ffffffffa04c4d2a&gt;] ?
      sblsnap_snap_now+0x25a/0x2a0 [sblsnap]<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: [&lt;ffffffffa04c4de4&gt;] ?
      sblsnap_patch_blkdev+0x74/0x120 [sblsnap]<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: [&lt;ffffffffa04c4eaf&gt;] ?
      sblsnap_get_snapshot+0x1f/0x60 [sblsnap]<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: [&lt;ffffffffa04c4f59&gt;] ?
      sblsnap_create_snapshot+0x69/0x120 [sblsnap]<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: [&lt;ffffffffa04c53cb&gt;] ?
      sblsnap_config_write+0x26b/0x2c0 [sblsnap]<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: [&lt;ffffffff81200343&gt;] ?
      proc_file_write+0x73/0xb0<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: [&lt;ffffffff812002d0&gt;] ?
      proc_file_write+0x0/0xb0<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: [&lt;ffffffff811f97c5&gt;] ?
      proc_reg_write+0x85/0xc0<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: [&lt;ffffffff81193318&gt;] ?
      vfs_write+0xb8/0x1a0<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: [&lt;ffffffff810e68b2&gt;] ?
      audit_syscall_entry+0x272/0x2a0<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: [&lt;ffffffff81193d21&gt;] ?
      sys_write+0x51/0x90<br>
    </tt><tt>Dec&nbsp; 7 15:52:20 dev2 kernel: [&lt;ffffffff8100b0b2&gt;] ?
      system_call_fastpath+0x16/0x1b<br>
      <br>
    </tt>
  </body>
</html>