From: Ingo Molnar <mingo@kernel.org>
To: akpm@linux-foundation.org
Cc: mm-commits@vger.kernel.org, alex.shi@intel.com, cpw@sgi.com,
hpa@zytor.com, jbeulich@suse.com, mingo@elte.hu,
tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: + uv-fix-incorrect-tlb-flush-all-issue.patch added to -mm tree
Date: Thu, 27 Sep 2012 08:44:56 +0200 [thread overview]
Message-ID: <20120927064456.GC5996@gmail.com> (raw)
In-Reply-To: <20120926223058.F0844100047@wpzn3.hot.corp.google.com>
* akpm@linux-foundation.org <akpm@linux-foundation.org> wrote:
> The flush tlb optimization code has logical issue on UV
> platform. It doesn't flush the full range at all, since it
> simply ignores its 'end' parameter (and hence also the "all"
> indicator) in uv_flush_tlb_others() function.
In other words it's a user-space data corruptor showstopper bug
fix for the UV platform, which should get high tip:x86/urgent
priority, right?
It's generally useful to put such info right into the patch
title. 'fix issue' sounds a tad too harmless.
Thanks,
Ingo
parent reply other threads:[~2012-09-27 6:45 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20120926223058.F0844100047@wpzn3.hot.corp.google.com>]
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=20120927064456.GC5996@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alex.shi@intel.com \
--cc=cpw@sgi.com \
--cc=hpa@zytor.com \
--cc=jbeulich@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mm-commits@vger.kernel.org \
--cc=tglx@linutronix.de \
/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