All of lore.kernel.org
 help / color / mirror / Atom feed
From: Don Brace <brace77070@gmail.com>
To: Bart Van Assche <bvanassche@acm.org>,
	James Bottomley <jbottomley@parallels.com>,
	Christoph Hellwig <hch@infradead.org>
Cc: Hannes Reinecke <hare@suse.de>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH for v3.19, v2] Avoid that sd_shutdown() triggers a kernel warning
Date: Thu, 15 Jan 2015 09:23:17 -0600	[thread overview]
Message-ID: <54B7DB65.2070502@gmail.com> (raw)
In-Reply-To: <54AD2E9A.50709@acm.org>

On 01/07/2015 07:03 AM, Bart Van Assche wrote:
> Since kernel v3.19-rc1 module_refcount() returns 1 instead of 0
> when called from inside module_exit(). This breaks the
> module_refcount() test in scsi_device_put() and hence causes the
> following kernel warning to be reported when unloading the ib_srp
> kernel module:
>

Tested-by: Don Brace <don.brace@pmcs.com>

This patch fixed module removal crashes I was seeing with the hpsa 
driver running on 3.19-rc4 kernel. Ran ~200 insmod/rmmod tests with no 
issues.


      parent reply	other threads:[~2015-01-15 15:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-07 13:03 [PATCH for v3.19, v2] Avoid that sd_shutdown() triggers a kernel warning Bart Van Assche
2015-01-08 13:15 ` Christoph Hellwig
2015-01-12 16:29   ` Alan Stern
2015-01-14  9:33     ` Christoph Hellwig
2015-01-14 15:07       ` Alan Stern
2015-01-14 15:07         ` Alan Stern
2015-01-15 16:06         ` Christoph Hellwig
2015-01-15 18:22           ` sysfs methods can race with ->remove Alan Stern
2015-01-15 19:40             ` Tejun Heo
2015-01-26 17:19               ` Christoph Hellwig
2015-01-26 18:38                 ` Alan Stern
2015-01-20 15:11       ` [PATCH for v3.19, v2] Avoid that sd_shutdown() triggers a kernel warning Alan Stern
2015-01-15 15:23 ` Don Brace [this message]

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=54B7DB65.2070502@gmail.com \
    --to=brace77070@gmail.com \
    --cc=bvanassche@acm.org \
    --cc=hare@suse.de \
    --cc=hch@infradead.org \
    --cc=jbottomley@parallels.com \
    --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.