From: Andrew Morton <akpm@linux-foundation.org>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Matthew Wilcox <matthew@wil.cx>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Greg KH <gregkh@suse.de>,
linux-usb-devel@lists.sourceforge.net,
linux-pm@lists.linux-foundation.org,
Bjorn Helgaas <bjorn.helgaas@hp.com>
Subject: Re: WARNING: at kernel/resource.c:189 __release_resource
Date: Mon, 26 Nov 2007 22:05:38 -0800 [thread overview]
Message-ID: <20071126220538.1aed9c33.akpm@linux-foundation.org> (raw)
In-Reply-To: <4745F77C.7040402@gmail.com>
On Thu, 22 Nov 2007 22:41:16 +0100 Jiri Slaby <jirislaby@gmail.com> wrote:
> Hi,
>
> Step aside. What's the purpose of having two similar patches for one issue,
> it then warns about the same thing twice:
> make-sure-nobodys-leaking-resources.patch
> releasing-resources-with-children.patch
Oh well. It's better than having none. Matthew, could you have think
about something for mainline please?
> Ok, I hit the bug, suspend of 00:06 device complains about it:
> WARNING: at .../kernel/resource.c:185 __release_resource()
>
> Call Trace:
> [<ffffffff8023f7b5>] release_resource+0xb5/0xf0
> [<ffffffff8036cda0>] pnp_release_resources+0x70/0x130
> [<ffffffff8036db85>] pnp_stop_dev+0x45/0x90
> [<ffffffff8036c942>] pnp_bus_suspend+0x92/0xb0
> [<ffffffff803b9f73>] suspend_device+0x113/0x180
> [<ffffffff803ba330>] device_suspend+0x200/0x320
> [<ffffffff80266905>] suspend_devices_and_enter+0xa5/0x170
> [<ffffffff80266bd9>] enter_state+0x209/0x270
> [<ffffffff80266cef>] state_store+0xaf/0xf0
> [<ffffffff8032ca67>] kobj_attr_store+0x17/0x20
> [<ffffffff802e459e>] sysfs_write_file+0xce/0x140
> [<ffffffff80299cc7>] vfs_write+0xc7/0x170
> [<ffffffff8029a360>] sys_write+0x50/0x90
> [<ffffffff8020bcde>] system_call+0x7e/0x83
>
> # LANG=en ll /sys/devices/pnp0/00:06/
> total 0
> lrwxrwxrwx 1 root root 0 Nov 22 22:35 driver -> ../../../bus/pnp/drivers/serial
> -r--r--r-- 1 root root 4096 Nov 22 22:35 id
> -r--r--r-- 1 root root 4096 Nov 22 22:35 options
> drwxr-xr-x 2 root root 0 Nov 22 22:35 power
> -rw-r--r-- 1 root root 4096 Nov 22 22:35 resources
> lrwxrwxrwx 1 root root 0 Nov 22 22:35 subsystem -> ../../../bus/pnp
> drwxr-xr-x 3 root root 0 Nov 22 22:35 tty
> -rw-r--r-- 1 root root 4096 Nov 22 22:35 uevent
>
I suppose that's a genuine leak, presumably in 8250_pnp.
next prev parent reply other threads:[~2007-11-27 6:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-22 21:41 WARNING: at kernel/resource.c:189 __release_resource Jiri Slaby
2007-11-27 6:05 ` Andrew Morton [this message]
2007-11-27 12:38 ` Matthew Wilcox
2007-11-29 23:40 ` Bjorn Helgaas
2007-11-30 0:42 ` Andrew Morton
2007-11-30 21:08 ` Bjorn Helgaas
2007-11-30 22:49 ` Jiri Slaby
2007-11-30 22:58 ` Bjorn Helgaas
2007-12-01 8:12 ` Jiri Slaby
2007-12-01 12:00 ` Jiri Slaby
2007-12-05 18:24 ` RFC: PNP: do not stop/start devices in suspend/resume path Bjorn Helgaas
2007-12-05 18:50 ` Matthew Wilcox
2007-12-06 1:07 ` Rafael J. Wysocki
2007-12-06 23:25 ` Bjorn Helgaas
2007-12-12 8:16 ` Andrew Morton
2007-12-12 16:29 ` Bjorn Helgaas
2007-12-13 8:26 ` Pierre Ossman
2007-12-07 7:13 ` RFC: " Shaohua Li
2007-12-10 23:26 ` Bjorn Helgaas
2007-12-24 1:43 ` do not stop/start devices in suspend/resume path: the SCSI case Stephane Ascoet
2007-12-24 3:21 ` Bjorn Helgaas
2007-12-01 21:01 ` WARNING: at kernel/resource.c:189 __release_resource Pierre Ossman
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=20071126220538.1aed9c33.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bjorn.helgaas@hp.com \
--cc=gregkh@suse.de \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=matthew@wil.cx \
/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).