From: Ingo Molnar <mingo@elte.hu>
To: Andi Kleen <andi@firstfloor.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, jkosina@suse.cz,
zdenek.kabelac@gmail.com
Subject: Re: [PATCH REPOST^3] Run IST traps from user mode preemptive on process stack
Date: Tue, 6 May 2008 16:41:27 +0200 [thread overview]
Message-ID: <20080506144127.GB26281@elte.hu> (raw)
In-Reply-To: <87skwvbn4m.fsf@basil.nowhere.org>
* Andi Kleen <andi@firstfloor.org> wrote:
> Thomas Gleixner <tglx@linutronix.de> writes:
>
> > On Fri, 2 May 2008, Andi Kleen wrote:
> >> [Fixes a bug originally introduced in 2.6.23 I think. Reposted many times
> >> so far, but still not applied. Please apply.]
> >
> > The print_vma_addr() bug was introduced by commit 03252919 (by you) in
> > the 2.6.25 merge window and we fixed it before 25-rc2 via commit e8bff74a.
hm, why did you cut out and ignore this question from Thomas:
> > Do you know about any other breakage in that code? If not, why do
> > you claim that we ignored a bug fix?
First you are putting pressure on us by innuendo that we somehow did not
react to an unfixed x86 bug, supposedly starting in v2.6.23 and still
not fixed in v2.6.26 as we speak. This is a pretty serious accusation!
But, if one looks closer, your accusation does not hold up to scrutiny:
it turns out that it is not in v2.6.23 but v2.6.25, that it got fixed
within 2 weeks between v2.6.25-rc1 and v2.6.25-rc2, that it is not an
unfixed bug that we ignored but at most about a small detail in a debug
feature introduced by _you_.
Why are you doing this with us? First you are accusing us and then you
are ignoring straight questions that would clear us from your unfair
accusation. Why?
Ingo
prev parent reply other threads:[~2008-05-06 14:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 9:19 Andi Kleen
2008-05-06 12:31 ` Thomas Gleixner
2008-05-06 13:03 ` Andi Kleen
2008-05-06 14:34 ` Ingo Molnar
2008-05-06 14:39 ` Ingo Molnar
2008-05-06 14:41 ` Ingo Molnar [this message]
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=20080506144127.GB26281@elte.hu \
--to=mingo@elte.hu \
--cc=andi@firstfloor.org \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=zdenek.kabelac@gmail.com \
/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®