From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: Andi Kleen <ak@suse.de>
Cc: "Siddha, Suresh B" <suresh.b.siddha@intel.com>,
Andrew Morton <akpm@osdl.org>,
discuss@x86-64.org, linux-kernel@vger.kernel.org,
nanhai.zou@intel.com, rohit.seth@intel.com,
rajesh.shah@intel.com
Subject: Re: [discuss] Re: [Patch] x86_64: TASK_SIZE fixes for compatibility mode processes
Date: Fri, 3 Jun 2005 12:09:14 -0700 [thread overview]
Message-ID: <20050603120913.C29609@unix-os.sc.intel.com> (raw)
In-Reply-To: <20050603154839.GN23831@wotan.suse.de>; from ak@suse.de on Fri, Jun 03, 2005 at 05:48:39PM +0200
On Fri, Jun 03, 2005 at 05:48:39PM +0200, Andi Kleen wrote:
> On Thu, Jun 02, 2005 at 04:06:04PM -0700, Siddha, Suresh B wrote:
> > On Thu, Jun 02, 2005 at 03:48:23PM -0700, Andrew Morton wrote:
> > > I know. I'm claiming that this is conceptually wrong.
> >
> > I def see your point. But this is too late for 2.6.12. We want to get this
> > fixed in 2.6.12. We can do the cleanup at a more convenient time.
>
> My feeling is that all of this is more for post 2.6.12. I still
> have not seen anything important that would get fixed by it.
Andi, This patch fixes two critical issues. One is the memory leak that
can happen in syscall32_setup_pages because of a malicious app and
another is the 32bit hugetlb application failure(which was also observed
by a customer recently). More details are in my changeset comments.
Either we need to fix these issues independently for 2.6.12 or address
the issue globally(fixing all the corner cases).
thanks,
suresh
next prev parent reply other threads:[~2005-06-03 19:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-02 20:32 [Patch] x86_64: TASK_SIZE fixes for compatibility mode processes Siddha, Suresh B
2005-06-02 20:50 ` Andrew Morton
2005-06-02 22:19 ` Siddha, Suresh B
2005-06-02 22:48 ` Andrew Morton
2005-06-02 23:06 ` [discuss] " Siddha, Suresh B
2005-06-03 15:48 ` Andi Kleen
2005-06-03 19:09 ` Siddha, Suresh B [this message]
2005-06-05 11:17 ` Andi Kleen
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=20050603120913.C29609@unix-os.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nanhai.zou@intel.com \
--cc=rajesh.shah@intel.com \
--cc=rohit.seth@intel.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 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.