public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Varun Prakash <varun@chelsio.com>
To: Christoph Hellwig <hch@lst.de>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] csiostor: switch to pci_alloc_irq_vectors
Date: Tue, 4 Apr 2017 13:49:44 +0530	[thread overview]
Message-ID: <20170404081943.GA1665@chelsio.com> (raw)
In-Reply-To: <20170404064614.GA9275@lst.de>

On Tue, Apr 04, 2017 at 08:46:14AM +0200, Christoph Hellwig wrote:
> Does this one work better?
>

csiostor driver is triggering following warning during module unload.

WARNING: CPU: 8 PID: 20636 at kernel/irq/manage.c:1480 __free_irq+0xa6/0x2b0
Trying to free already-free IRQ 53
CPU: 8 PID: 20636 Comm: rmmod Tainted: G    B   W  OE   4.11.0-rc5+ #2
Call Trace:
dump_stack+0x63/0x84
__warn+0xd1/0xf0
warn_slowpath_fmt+0x5f/0x80
__free_irq+0xa6/0x2b0
free_irq+0x39/0x90
csio_free_irqs+0x34/0x90 [csiostor]
csio_hw_free+0x12/0xb0 [csiostor]
csio_remove_one+0x6e/0x90 [csiostor]
pci_device_remove+0x39/0xc0
device_release_driver_internal+0x141/0x1f0
driver_detach+0x3f/0x80
bus_remove_driver+0x55/0xd0
driver_unregister+0x2c/0x50
pci_unregister_driver+0x2a/0xa0
csio_exit+0x10/0xf70 [csiostor]
SyS_delete_module+0x1ba/0x220
do_syscall_64+0x67/0x180
entry_SYSCALL64_slow_path+0x25/0x25

kernel/irq/manage.c:1480
1457 static struct irqaction *__free_irq(unsigned int irq, void *dev_id)
1458 {
1459         struct irq_desc *desc = irq_to_desc(irq);
1460         struct irqaction *action, **action_ptr;
1461         unsigned long flags;
1462
	     ...
1475         action_ptr = &desc->action;
1476         for (;;) {
1477                 action = *action_ptr;
1478
1479                 if (!action) {
1480                         WARN(1, "Trying to free already-free IRQ %d\n", irq);
1481                         raw_spin_unlock_irqrestore(&desc->lock, flags);
1482                         chip_bus_sync_unlock(desc);
1483                         return NULL;
1484                 }
1485
1486                 if (action->dev_id == dev_id)
1487                         break;
1488                 action_ptr = &action->next;
1489         }
	     ...
1546 }

  reply	other threads:[~2017-04-04  8:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-13 16:30 [PATCH] csiostor: switch to pci_alloc_irq_vectors Christoph Hellwig
2017-01-21  0:27 ` Martin K. Petersen
2017-03-31  6:55   ` Christoph Hellwig
2017-04-03 14:51     ` Varun Prakash
2017-04-04  6:46       ` Christoph Hellwig
2017-04-04  8:19         ` Varun Prakash [this message]
2017-04-05  6:26           ` Christoph Hellwig
2017-04-05 15:39             ` Varun Prakash
2017-04-06  7:58               ` Christoph Hellwig
2017-04-06 15:26                 ` Varun Prakash
2017-04-06 16:58                 ` 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=20170404081943.GA1665@chelsio.com \
    --to=varun@chelsio.com \
    --cc=hch@lst.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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