From: David Gordon Hogan <dhog@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] dhog the corruptor!
Date: Tue, 13 Nov 2001 18:53:02 -0500 [thread overview]
Message-ID: <20011113235305.B831F19A46@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 114 bytes --]
It's not quite the same. No ``thunks'' here. All the references
are resolved at load time with this schema.
[-- Attachment #2: Type: message/rfc822, Size: 2215 bytes --]
From: "Chris Hollis-Locke" <chris@cjl1.demon.co.uk>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] dhog the corruptor!
Date: Tue, 13 Nov 2001 23:38:46 -0000
Message-ID: <008701c16c9c$57155b80$2248dec2@falken>
> Brucee's implementation just patches the call to point to the
> correct destination. You don't have to walk any machine code.
MS VXDs work in a similar way - they call it something like
'snap' linkage. The 'unlinked' call is to a lookup function that
patches the caller (determined by return addr on the stack) to
the actual entry point. The downside is that you cannot easily
unload or replace a driver that is linked in such a way, which
explains why there are so many "You must now reboot your computer"
messages.
The new WDM may do things differently, I haven't looked at that yet.
next reply other threads:[~2001-11-13 23:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 23:53 David Gordon Hogan [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-14 9:26 forsyth
2001-11-16 11:56 ` Boyd Roberts
2001-11-13 23:54 forsyth
2001-11-13 23:50 David Gordon Hogan
2001-11-14 0:34 ` Quinn Dunkan
2001-11-14 4:46 ` Lucio De Re
2001-11-16 11:52 ` Boyd Roberts
2001-11-13 23:04 David Gordon Hogan
2001-11-13 23:28 ` Quinn Dunkan
2001-11-13 23:38 ` Chris Hollis-Locke
2001-11-13 22:53 anothy
2001-11-13 22:59 ` George Michaelson
2001-11-13 22:32 David Gordon Hogan
2001-11-13 22:09 anothy
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=20011113235305.B831F19A46@mail.cse.psu.edu \
--to=dhog@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).