From: Andi Kleen <ak@suse.de>
To: Zachary Amsden <zach@vmware.com>
Cc: Ingo Molnar <mingo@elte.hu>,
virtualization@lists.osdl.org, Andrew Morton <akpm@osdl.org>,
Chris Wright <chrisw@osdl.org>,
Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Zwane Mwaikambo <zwane@arm.linux.org.uk>,
Martin Bligh <mbligh@mbligh.org>,
Pratap Subrahmanyam <pratap@vmware.com>,
Christopher Li <chrisl@vmware.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
prasanna@in.ibm.com, ananth@in.ibm.com,
anil.s.keshavamurthy@intel.com, davem@davemloft.net
Subject: Re: [PATCH 19/21] i386 Kprobes semaphore fix
Date: Fri, 11 Nov 2005 16:27:13 +0100 [thread overview]
Message-ID: <200511111627.14403.ak@suse.de> (raw)
In-Reply-To: <43723768.2060103@vmware.com>
On Wednesday 09 November 2005 18:52, Zachary Amsden wrote:
> Well, if there is a justification for it, that means we really should
> handle all the nasty EIP conversion cases due to segmentation and v8086
> mode in the kprobes code. I was hoping that might not be the case.
Or just forbid kprobes for 16bit processes (or anything running in a non GDT
code segment). Would be perfectly reasonable IMHO.
-Andi
next prev parent reply other threads:[~2005-11-11 15:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 4:39 [PATCH 19/21] i386 Kprobes semaphore fix Zachary Amsden
2005-11-08 13:12 ` Andi Kleen
2005-11-08 13:36 ` Zachary Amsden
2005-11-09 13:38 ` Andi Kleen
2005-11-09 16:46 ` Zachary Amsden
2005-11-09 16:58 ` Ingo Molnar
2005-11-09 17:52 ` Zachary Amsden
2005-11-10 18:09 ` Prasanna S Panchamukhi
2005-11-10 14:58 ` Zachary Amsden
2005-11-10 16:16 ` H. Peter Anvin
2005-11-11 15:27 ` Andi Kleen [this message]
2005-11-11 15:25 ` Andi Kleen
2005-11-14 5:54 ` Prasanna S Panchamukhi
[not found] ` <20051109093755.GA10361@in.ibm.com>
2005-11-10 16:33 ` Prasanna S Panchamukhi
[not found] <20051108074430.GG28201@elte.hu>
2005-11-08 13:26 ` Zachary Amsden
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=200511111627.14403.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=ananth@in.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=chrisl@vmware.com \
--cc=chrisw@osdl.org \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@mbligh.org \
--cc=mingo@elte.hu \
--cc=prasanna@in.ibm.com \
--cc=pratap@vmware.com \
--cc=torvalds@osdl.org \
--cc=virtualization@lists.osdl.org \
--cc=zach@vmware.com \
--cc=zwane@arm.linux.org.uk \
/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.