From: Greg KH <gregkh@linuxfoundation.org>
To: "Winkler, Tomas" <tomas.winkler@intel.com>
Cc: "arnd@arndb.de" <arnd@arndb.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Usyskin, Alexander" <alexander.usyskin@intel.com>
Subject: Re: [char-misc-next 4/5] mei: nfc: clean nfc internal struct on host exit
Date: Sun, 20 Jul 2014 08:25:12 -0700 [thread overview]
Message-ID: <20140720152512.GA31382@kroah.com> (raw)
In-Reply-To: <5B8DA87D05A7694D9FA63FD143655C1B1C379CCB@HASMSX106.ger.corp.intel.com>
On Sun, Jul 20, 2014 at 06:30:16AM +0000, Winkler, Tomas wrote:
> > > @@ -553,6 +553,7 @@ void mei_nfc_host_exit(struct mei_device *dev)
> > > {
> > > struct mei_nfc_dev *ndev = &nfc_dev;
> > > cancel_work_sync(&ndev->init_work);
> > > + memset(ndev, 0, sizeof(struct mei_nfc_dev));
> >
> > This implies that something is using a "static" device structure, which
> > isn't allowed by the driver core. So please fix the root cause here,
> > don't paper over the bug.
> >
> You are partially correct as this is not the 'struct device' it just a nfc singleton in any case it is not really nice
> and we have the fix in queue but it is rather extensive rework and I guess it won't be suitable for stable
> so hence this one liner fix.
It shouldn't be a huge rework to make a static variable dynamic, right?
Please do it correctly.
thanks,
greg k-h
prev parent reply other threads:[~2014-07-20 15:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 7:53 [char-misc-next 0/5] mei: corner cases bug fixes Tomas Winkler
[not found] ` <1405583618-8229-5-git-send-email-tomas.winkler@intel.com>
2014-07-18 1:37 ` [char-misc-next 4/5] mei: nfc: clean nfc internal struct on host exit Greg KH
2014-07-20 6:30 ` Winkler, Tomas
2014-07-20 15:25 ` Greg KH [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=20140720152512.GA31382@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.usyskin@intel.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tomas.winkler@intel.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