public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: David C Somayajulu <david.somayajulu@qlogic.com>
Cc: linux-scsi@vger.kernel.org, open-iscsi@googlegroups.com,
	Mike Christie <michaelc@cs.wisc.edu>
Subject: Re: [PATCH] qla4xxx: bug fixes
Date: Sat, 27 Jan 2007 10:08:22 -0600	[thread overview]
Message-ID: <1169914102.4392.5.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <1169497571.12416.2.camel@linux-58to>

On Mon, 2007-01-22 at 12:26 -0800, David C Somayajulu wrote:
> The included patch fixes the following issues:
> 1. qla3xxx/qla4xxx co-existence issue which can result in a lockup when qla3xxx driver is unloaded, or when ifdown; ifup is performed on one of the interfaces correponding to qla3xxx. This is because qla4xxx HBA supports one ethernet and iscsi interfaces per port. Both iscsi and ethernet interfaces share the same state machine. The problem has to do with synchronizing access to the state machine in the event of a reset
> 2. mutex_lock() is sometimes not followed by mutex_unlock() prior to invoking a msleep() in qla4xxx_mailbox_command()

Git applymbox picked up this nasty (which I've corrected):

Applying 'qla4xxx: bug fixes'

Space in indent is followed by a tab.
.dotest/patch:122:                      set_bit(AF_MBOX_COMMAND,
&ha->flags);
Space in indent is followed by a tab.
.dotest/patch:123:                      mutex_unlock(&ha->mbox_sem);
Space in indent is followed by a tab.
.dotest/patch:124:                      break;
Space in indent is followed by a tab.
.dotest/patch:125:              }
Space in indent is followed by a tab.
.dotest/patch:126:              mutex_unlock(&ha->mbox_sem);
warning: squelched 7 whitespace errors
warning: 12 lines add trailing whitespaces.

James



  reply	other threads:[~2007-01-27 16:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-22 20:26 [PATCH] qla4xxx: bug fixes David C Somayajulu
2007-01-27 16:08 ` James Bottomley [this message]
2007-01-29 18:34   ` David Somayajulu

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=1169914102.4392.5.camel@mulgrave.il.steeleye.com \
    --to=james.bottomley@steeleye.com \
    --cc=david.somayajulu@qlogic.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    --cc=open-iscsi@googlegroups.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