All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 8213] Race: a lock is expected before calling BusLogic_WriteOutgoingMailbox, but it is not held in some case and it is held in other cases
Date: Sat, 29 Aug 2009 15:53:59 GMT	[thread overview]
Message-ID: <200908291553.n7TFrx3E009145@demeter.kernel.org> (raw)
In-Reply-To: <bug-8213-11613@http.bugzilla.kernel.org/>

http://bugzilla.kernel.org/show_bug.cgi?id=8213


Lin Tan <tammy000@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Kernel Version|2.6.20.1                    |2.6.30.5
         Regression|---                         |No




--- Comment #3 from Lin Tan <tammy000@gmail.com>  2009-08-29 15:53:57 ---
Thanks, Roland.

I checked the latest version (2.6.30.5) on the Linux cross reference, and the
problem still applies. 

Actually, I found that the host_lock is explicitly released before calling
scsi_dispatch_cmd(). See below.

1474 static void scsi_request_fn(struct request_queue *q)
1475 { 
...
1563                 spin_unlock_irq(shost->host_lock);
1564
1565                /*
1566                 * Finally, initialize any error handling parameters, and
set up
1567                 * the timers for timeouts.
1568                 */
1569                scsi_init_cmd_errh(cmd);
1570
1571                /*
1572                 * Dispatch the command to the low-level driver.
1573                 */
1574                rtn = scsi_dispatch_cmd(cmd);
1575           
...

BTW, one clarification, BusLogic_WriteOutgoingMailbox was called twice in
BusLogic_QueueCommand. The first one is what I meant in the original report. It
is NOT called with the host lock held. The second invocation is fine.

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2009-08-29 15:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-8213-11613@http.bugzilla.kernel.org/>
2009-08-29  9:29 ` [Bug 8213] Race: a lock is expected before calling BusLogic_WriteOutgoingMailbox, but it is not held in some case and it is held in other cases bugzilla-daemon
2009-08-29 16:13   ` James Bottomley
2009-08-29 15:53 ` bugzilla-daemon [this message]
2009-08-29 16:14 ` bugzilla-daemon
2009-08-29 16:36 ` bugzilla-daemon

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=200908291553.n7TFrx3E009145@demeter.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-scsi@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 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.