From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: "James E.J. Bottomley" <jejb@linux.ibm.com>,
Naresh Kumar Inna <naresh@chelsio.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] scsi: csiostor: Don't enable IRQs too early
Date: Fri, 25 Oct 2019 01:14:11 +0000 [thread overview]
Message-ID: <yq1pnilbp98.fsf@oracle.com> (raw)
In-Reply-To: <20191019085913.GA14245@mwanda> (Dan Carpenter's message of "Sat, 19 Oct 2019 11:59:13 +0300")
Dan,
> These are called with IRQs disabled from csio_mgmt_tmo_handler() so we
> can't call spin_unlock_irq() or it will enable IRQs prematurely.
Applied to 5.5/scsi-queue, thanks!
--
Martin K. Petersen Oracle Linux Engineering
WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: "James E.J. Bottomley" <jejb@linux.ibm.com>,
Naresh Kumar Inna <naresh@chelsio.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] scsi: csiostor: Don't enable IRQs too early
Date: Thu, 24 Oct 2019 21:14:11 -0400 [thread overview]
Message-ID: <yq1pnilbp98.fsf@oracle.com> (raw)
In-Reply-To: <20191019085913.GA14245@mwanda> (Dan Carpenter's message of "Sat, 19 Oct 2019 11:59:13 +0300")
Dan,
> These are called with IRQs disabled from csio_mgmt_tmo_handler() so we
> can't call spin_unlock_irq() or it will enable IRQs prematurely.
Applied to 5.5/scsi-queue, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2019-10-25 1:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-19 8:59 [PATCH] scsi: csiostor: Don't enable IRQs too early Dan Carpenter
2019-10-19 8:59 ` Dan Carpenter
2019-10-25 1:14 ` Martin K. Petersen [this message]
2019-10-25 1:14 ` Martin K. Petersen
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=yq1pnilbp98.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=dan.carpenter@oracle.com \
--cc=jejb@linux.ibm.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=naresh@chelsio.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.