From: Dave Jones <davej@redhat.com>
To: Andi Kleen <ak@suse.de>
Cc: Chuck Ebbert <cebbert@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Multiple free during oprofile unload
Date: Fri, 25 May 2007 13:38:13 -0400 [thread overview]
Message-ID: <20070525173813.GA2875@redhat.com> (raw)
In-Reply-To: <200705251913.53097.ak@suse.de>
On Fri, May 25, 2007 at 07:13:52PM +0200, Andi Kleen wrote:
>
> >
> > So what, the alternative is leave oprofile busted in 2.6.21.x even longer?
>
> stable is about backporting _well tested_ patches from mainline.
>
> If the stable request comes in from someone 5 minutes after the mainline submission
> I don't see how that testing should happen.
And how many people have picked up on the fact that the fix in 2.6.22rc is busted
in the last week ?
Ie, we'd be waiting probably until after .22 goes out before we found out it's
still horked, and leaving .21.x busted for another three weeks.
If the functionality is completely busted in -stable, adding a patch that's
isolated to that component can't really make things much worse.
All we've done here is move the breakage.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2007-05-25 17:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-25 15:00 Multiple free during oprofile unload Chuck Ebbert
2007-05-25 15:42 ` Andi Kleen
2007-05-25 16:18 ` Dave Jones
2007-05-25 17:13 ` Andi Kleen
2007-05-25 17:38 ` Dave Jones [this message]
2007-05-25 18:02 ` Andi Kleen
2007-05-25 18:37 ` Alan Cox
2007-05-26 2:27 ` [PATCH] x86: fix oprofile double free (was Re: Multiple free during oprofile unload) Chris Wright
2007-05-26 7:43 ` Andi Kleen
2007-05-26 14:03 ` Chris Wright
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=20070525173813.GA2875@redhat.com \
--to=davej@redhat.com \
--cc=ak@suse.de \
--cc=cebbert@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.