From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Rolf Kutz <kutz@netcologne.de>,
244207@bugs.debian.org, Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Bug#244207: kernel-source-2.6.5: mwave gives warning on suspend
Date: Sat, 17 Apr 2004 12:48:50 +0100 [thread overview]
Message-ID: <20040417124850.C14786@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20040417113918.GA4846@gondor.apana.org.au>; from herbert@gondor.apana.org.au on Sat, Apr 17, 2004 at 09:39:18PM +1000
On Sat, Apr 17, 2004 at 09:39:18PM +1000, Herbert Xu wrote:
> On Sat, Apr 17, 2004 at 12:43:11PM +0200, Rolf Kutz wrote:
> > Package: kernel-source-2.6.5
> > Version: 2.6.5-1
> > Severity: normal
> >
> > The mwave module gives the following warning on suspend:
> >
> > Apr 16 09:55:13 localhost kernel: Device 'mwave' does not have a release() funct
> > ion, it is broken and must be fixed.
> > Apr 16 09:55:13 localhost kernel: Badness in device_release at drivers/base/core
> > .c:85
>
> Thanks for the report.
>
> This patch should shut the warning up.
And that's all it does. It doesn't stop the oops which potentically can
happen when the struct device is freed (by the module being unloaded)
while there is still a reference to the struct device.
This is the whole point of the warning - to warn that the necessary
release functionality is not present, and that the way the device
is being used is buggy.
Providing an empty release function is not a solution - it merely papers
over the warning leaving the real bug behind.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2004-04-17 11:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040417104311.9C13A1D802@jamaika.kutz.dyndns.org>
2004-04-17 11:39 ` Bug#244207: kernel-source-2.6.5: mwave gives warning on suspend Herbert Xu
2004-04-17 11:48 ` Russell King [this message]
2004-04-17 12:23 ` Herbert Xu
2004-04-17 12:29 ` Herbert Xu
2004-04-18 10:31 ` Herbert Xu
2004-04-18 11:17 ` Christoph Hellwig
2004-04-18 11:32 ` Christoph Hellwig
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=20040417124850.C14786@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=244207@bugs.debian.org \
--cc=akpm@osdl.org \
--cc=herbert@gondor.apana.org.au \
--cc=kutz@netcologne.de \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox