From: Tejun Heo <tj@kernel.org>
To: Andrew Lutomirski <luto@mit.edu>
Cc: Matt Helsley <matthltc@us.ibm.com>,
Pavel Emelyanov <xemul@parallels.com>,
Nathan Lynch <ntl@pobox.com>, Oren Laadan <orenl@cs.columbia.edu>,
Daniel Lezcano <dlezcano@fr.ibm.com>,
S@mit.edu, "James E.J. Bottomley" <JBottomley@parallels.com>,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [EXAMPLE CODE] Parasite thread injection and TCP connection hijacking
Date: Sat, 6 Aug 2011 15:20:52 +0200 [thread overview]
Message-ID: <20110806132052.GE23937@htj.dyndns.org> (raw)
In-Reply-To: <CAObL_7FeZQpnOzpXHqSviZdBRUCL+rODbQOBb+6JPSd3PB=fig@mail.gmail.com>
Hello,
On Sat, Aug 06, 2011 at 09:15:45AM -0400, Andrew Lutomirski wrote:
> On Sat, Aug 6, 2011 at 9:00 AM, Tejun Heo <tj@kernel.org> wrote:
> > Actually, the only thing we need on x86_64 is two bytes for the
> > syscall instruction because all params are passed through registers
> > anyway. We can just set up parameters for mmap, turn on single step,
> > point %rip to syscall in the vsyscall page. So, either way, I don't
> > think this would be too difficult to solve.
>
> Not any more -- that syscall instruction is gone as of 3.1. You could
> search through the vdso to find a syscall, but that seems fragile.
>
> Why not just add a ptrace command to issue a syscall?
Yeah, maybe. If this thing proves to be useful enough and looking for
a page to poke under proc too cumbersome. I'm not against it but
don't really see strong need either at this point.
Thanks.
--
tejun
next prev parent reply other threads:[~2011-08-06 13:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-06 12:12 [EXAMPLE CODE] Parasite thread injection and TCP connection hijacking Tejun Heo
2011-08-06 12:45 ` Andy Lutomirski
2011-08-06 13:00 ` Tejun Heo
2011-08-06 13:15 ` Andrew Lutomirski
2011-08-06 13:20 ` Tejun Heo [this message]
2011-08-08 10:20 ` Tejun Heo
2011-10-30 4:48 ` hiberante hangs TCP " David Fries
2011-10-30 20:16 ` Tejun Heo
2011-10-30 20:43 ` David Fries
2011-11-02 9:44 ` MyungJoo Ham
2011-11-02 15:10 ` Tejun Heo
2012-02-17 19:28 ` Pavel Machek
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=20110806132052.GE23937@htj.dyndns.org \
--to=tj@kernel.org \
--cc=JBottomley@parallels.com \
--cc=S@mit.edu \
--cc=davem@davemloft.net \
--cc=dlezcano@fr.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@mit.edu \
--cc=matthltc@us.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=ntl@pobox.com \
--cc=orenl@cs.columbia.edu \
--cc=xemul@parallels.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;
as well as URLs for NNTP newsgroup(s).