From: Borislav Petkov <bp@alien8.de>
To: Simon Kirby <sim@hostway.ca>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [3.1-rc6] kmalloc(64) leak from IDE
Date: Tue, 27 Sep 2011 19:07:55 +0200 [thread overview]
Message-ID: <20110927170755.GA31384@gere.osrc.amd.com> (raw)
In-Reply-To: <20110926080549.GA14697@hostway.ca>
(forgot to Cc linux-ide earlier, sorry)
On Mon, Sep 26, 2011 at 01:05:50AM -0700, Simon Kirby wrote:
> Ok, good. It's still running without any problem, and no new leaks
> reported.
Ok.
[..]
> > backporting it to -stable is a good point. I'll add the proper tagging
> > to the patch.
>
> Do you know in which version the issue started, then?
>
> If not, all I have to start with is that it was fine on 2.6.36, and I can
> bisect it, if that would help.
This is exactly the question: AFAICT, it could be that changes in the
block layer at some point have caused the ide bust and since almost no
one tests ide...
The patch adding the dynamic ide_cmd struct allocation is
395d8ef5bebe547a80737692f9789d2e36da16f2 from 2008 and I don't think it
caused the issue then but I could also be remembering it wrong.
So I wouldn't bisect it but test stable trees after 2.6.36 to see
whether they have the issue, and if so, only then the patch should be
backported.
And this is not that easy now with k.org down but looking at
http://web.archive.org/web/20110725015737/http://kernel.org/
the only stable trees which need to be tested are 2.6.39 and 3.0.
How does that sound?
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2011-09-27 17:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 7:26 [3.1-rc6] kmalloc(64) leak from IDE Simon Kirby
2011-09-22 8:48 ` Borislav Petkov
2011-09-22 20:23 ` Simon Kirby
2011-09-23 7:21 ` Borislav Petkov
2011-09-23 15:58 ` Bernd Schubert
2011-09-23 16:08 ` Bjorn Helgaas
2011-09-23 16:34 ` Bernd Schubert
2011-09-23 16:40 ` Bjorn Helgaas
2011-09-23 17:49 ` Bernd Schubert
2011-09-23 17:38 ` Simon Kirby
2011-09-25 8:58 ` Borislav Petkov
2011-09-26 8:05 ` Simon Kirby
2011-09-27 17:07 ` Borislav Petkov [this message]
2011-09-29 9:27 ` Borislav Petkov
2011-09-29 22:45 ` Simon Kirby
2011-09-30 6:40 ` Borislav Petkov
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=20110927170755.GA31384@gere.osrc.amd.com \
--to=bp@alien8.de \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sim@hostway.ca \
/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