From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Fabio Comolli <fabio.comolli@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jay Fenlason <fenlason@redhat.com>
Subject: Re: Regression in 2.6.28-rc and 2.6.27-stable - hibernate related
Date: Mon, 24 Nov 2008 08:18:47 +0100 [thread overview]
Message-ID: <492A5557.2010404@s5r6.in-berlin.de> (raw)
In-Reply-To: <200811240031.55944.rjw@sisk.pl>
Rafael J. Wysocki wrote:
> On Sunday, 23 of November 2008, Fabio Comolli wrote:
>> Hi.
>>
>> On Sun, Nov 23, 2008 at 7:24 PM, Fabio Comolli <fabio.comolli@gmail.com> wrote:
>>> Hi
>>>
>>> Yes. I started another bisection session between 2.6.27.4 and 2.6.27.5.
>>>
>> Ok, this time things went much better. The bisection pointed to:
>>
>> ------------------------------------------------------------------------------------------------------------------------------------------------
>> fcomolli@hawking:~/software/GIT-TREES/linux-2.6.27.y> git bisect good
>> ff0f8d16839cd02dc95bd92c212cbd5d433a4d2b is first bad commit
>> commit ff0f8d16839cd02dc95bd92c212cbd5d433a4d2b
>> Author: Jay Fenlason <fenlason@redhat.com>
>> Date: Mon Oct 27 23:28:14 2008 +0100
>>
>> firewire: fix struct fw_node memory leak
>>
>> commit 77e557191701afa55ae7320d42ad6458a2ad292e upstream
>>
>> With the bus_resets patch applied, it is easy to see this memory leak
>> by repeatedly resetting the firewire bus while running slabtop in
>> another window. Just watch kmalloc-32 grow and grow...
>>
>> Signed-off-by: Jay Fenlason <fenlason@redhat.com>
>> Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
>>
>> :040000 040000 01cadbd5f5fb81ce4f5e2023573204c4fbec3a28
>> 809a53f4be87bd8be133ebd7564e1139a0cfa45b M drivers
>> ------------------------------------------------------------------------------------------------------------------------------------------------
>>
>> And this is the log:
>>
>> ------------------------------------------------------------------------------------------------------------------------------------------------
>> fcomolli@hawking:~/software/GIT-TREES/linux-2.6.27.y> git bisect log
>> git-bisect start
>> # good: [056c71459d3acf9fefcb2dc67abeef10e649d508] Linux 2.6.27.4
>> git-bisect good 056c71459d3acf9fefcb2dc67abeef10e649d508
>> # bad: [788a5f3f70e2a9c46020bdd3a195f2a866441c5d] Linux 2.6.27.5
>> git-bisect bad 788a5f3f70e2a9c46020bdd3a195f2a866441c5d
>> # bad: [7bdb542c453c14e54af9ebe5c4a827e4a678c47d] powerpc/numa: Make
>> memory reserve code more robust
>> git-bisect bad 7bdb542c453c14e54af9ebe5c4a827e4a678c47d
>> # good: [f29062d0ec12ee3a58c67228dc829574b4ced378] syncookies: fix
>> inclusion of tcp options in syn-ack
>> git-bisect good f29062d0ec12ee3a58c67228dc829574b4ced378
>> # good: [882491755d4c819de5bb593f04d06692185760aa] firewire: fix
>> ioctl() return code
>> git-bisect good 882491755d4c819de5bb593f04d06692185760aa
>> # bad: [baae4f5fd7a75bdfa70d374b738963053df2bcaa] firewire: fw-sbp2: fix races
>> git-bisect bad baae4f5fd7a75bdfa70d374b738963053df2bcaa
>> # bad: [ff0f8d16839cd02dc95bd92c212cbd5d433a4d2b] firewire: fix struct
>> fw_node memory leak
>> git-bisect bad ff0f8d16839cd02dc95bd92c212cbd5d433a4d2b
>> # good: [b6021579f54e5b6b31f03fe24de1208a2feb4aec] firewire: Survive
>> more than 256 bus resets
>> git-bisect good b6021579f54e5b6b31f03fe24de1208a2feb4aec
>> ------------------------------------------------------------------------------------------------------------------------------------------------
>>
>> The commit reverted cleanly and now I'm running 2.6.27.7 with that
>> commit reverted. I'll post my results.
>>
>> Hoper this helps. Regards,
>
> Yes, thanks for bisecting this (CCs added).
The commit which was pointed to in the bisection does nothing else than
free some data in firewire-core.
(Note to myself and Jay: See http://lkml.org/lkml/2008/11/23/123 and
http://lkml.org/lkml/2008/11/23/153 for the history of this bug.)
Fabio, please test a _bad_ kernel with firewire drivers unloaded before
hibernation. Also, please enable in the "Kernel hacking" kernel config
menu: "Kernel debugging", "Debug slab memory allocations". Thanks,
--
Stefan Richter
-=====-==--- =-== ==---
http://arcgraph.de/sr/
next prev parent reply other threads:[~2008-11-24 7:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-23 16:17 Regression in 2.6.28-rc and 2.6.27-stable - hibernate related Fabio Comolli
2008-11-23 18:14 ` Rafael J. Wysocki
2008-11-23 18:24 ` Fabio Comolli
2008-11-23 20:23 ` Fabio Comolli
2008-11-23 23:31 ` Rafael J. Wysocki
2008-11-24 7:18 ` Stefan Richter [this message]
2008-11-24 8:57 ` Fabio Comolli
2008-11-25 23:15 ` Rafael J. Wysocki
2008-11-25 23:31 ` Rafael J. Wysocki
2008-11-26 1:03 ` Stefan Richter
2008-11-26 8:19 ` Fabio Comolli
2008-11-26 12:28 ` Stefan Richter
2008-11-26 19:45 ` Fabio Comolli
2008-11-26 20:07 ` Stefan Richter
2008-11-26 23:02 ` Rafael J. Wysocki
2008-11-27 15:17 ` Fabio Comolli
2008-11-27 21:54 ` Fabio Comolli
2008-12-05 0:24 ` Rafael J. Wysocki
2008-12-12 18:58 ` Pavel Machek
2008-12-12 19:01 ` Fabio Comolli
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=492A5557.2010404@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=fabio.comolli@gmail.com \
--cc=fenlason@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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