From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Ondrej Zary <linux@rainbow-software.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] [RESEND] wd719x: add missing .module to wd719x_template
Date: Thu, 12 Feb 2015 07:09:03 -0800 [thread overview]
Message-ID: <1423753743.2147.4.camel@HansenPartnership.com> (raw)
In-Reply-To: <1423485501-5992-1-git-send-email-linux@rainbow-software.org>
On Mon, 2015-02-09 at 13:38 +0100, Ondrej Zary wrote:
> wd719x_template is missing the .module field, causing module refcount
> not to work, allowing to rmmod the driver while in use (mounted filesystem),
> causing an oops.
>
> Set .module to THIS_MODULE to fix the problem.
This requires a cc to stable, doesn't it?
James
next prev parent reply other threads:[~2015-02-12 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 12:38 [PATCH] [RESEND] wd719x: add missing .module to wd719x_template Ondrej Zary
2015-02-12 15:09 ` James Bottomley [this message]
2015-02-12 15:32 ` Ondrej Zary
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=1423753743.2147.4.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@rainbow-software.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).