From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andi Kleen <ak@suse.de>
Cc: Dave Jones <davej@redhat.com>, Chuck Ebbert <cebbert@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Multiple free during oprofile unload
Date: Fri, 25 May 2007 19:37:37 +0100 [thread overview]
Message-ID: <20070525193737.34609de2@the-village.bc.nu> (raw)
In-Reply-To: <200705252002.58967.ak@suse.de>
On Fri, 25 May 2007 20:02:58 +0200
Andi Kleen <ak@suse.de> wrote:
>
> > If the functionality is completely busted in -stable,
>
> It's not; e.g. it works great on my P4 testbox with 2.6.21
>
> > 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.
>
> I don't think stable is the right place for development.
I'd agree entirely with Dave - if you are applying a fix to something
that is currently totally broken which may make it work and which doesn't
affect any other bit of code then it goes into the stable tree.
Absolutes like "no xyz in the stable tree" don't work in the real world
with real users. Intelligence does.
next prev parent reply other threads:[~2007-05-25 18:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-25 15:00 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
2007-05-25 18:02 ` Andi Kleen
2007-05-25 18:37 ` Alan Cox [this message]
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=20070525193737.34609de2@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=ak@suse.de \
--cc=cebbert@redhat.com \
--cc=davej@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®