Changes

'''Compel''' is a utility to execute arbitrary code in a context of a foreign process. Compel is part of CRIU, and its sources are available from [https://github.com/xemul/criu/tree/criu-dev/compel the criu-dev branch of CRIU repo, subdirectory compel].

'''Compel''' is a utility to execute arbitrary code in a context of a foreign process. Compel is part of CRIU, and its sources are available from [https://github.com/checkpoint-restore/criu/tree/criu-dev/compel the criu-dev branch of CRIU repo, subdirectory compel].

The code to be executed is called '''parasite code'''. Once compiled with compel flags and packed, it can be executed in other task's context. Note the code is run in environment without glibc, thus it can not call the usual stdio/stdlib/etc. functions.

The code to be executed is called '''parasite code'''. Once compiled with compel flags and packed, it can be executed in other task's context. Note the code is run in environment without glibc, thus it can not call the usual stdio/stdlib/etc. functions.

</pre>

</pre>

Then link the parasite binary. Include all the .o files needed.  

 

Then link the parasite binary. Include all the .o files needed and compel std plugin by using compel linker script.

<pre>

<pre>

$ ld foo1.o foo2.o compel/plugins/std.built-in.o -T compel/arch/$ARCH/scripts/compel-pack.lds.S -o parasite.po  

$ ld $(compel ldflags) foo1.o foo2.o $(compel plugins) -o parasite.po  

</pre>

</pre>

=== Using libcompel.a library ===

=== Using libcompel.a library ===

Currently there is only one way to load the blob into victim task using libcompel.a, called ''c-header'' <ref>This is done for historical reasons, it was the most handy way to load [[parasite code]] by CRIU. In plans we have loading the .po ELF file itself</ref>. First you should make a header out of you .po file with the <code>hgen</code> action of compel tool:

Currently there is only one way to load the blob into victim task using libcompel.a, called ''c-header'' <ref>This is done for historical reasons. It was the most handy way to load [[parasite code]] by CRIU. In plans we have loading the .po ELF file itself</ref>. First you should make a header out of your .po file with the <code>hgen</code> action of compel tool:

  compel hgen -f parasite.po -p parasite -o parasite.h

  compel hgen -f parasite.po -o parasite.h

Options meaning is the following:

Options meaning is the following:

* <code>-f</code> tells which binary to turn into header

* <code>-f</code> tells which binary to turn into header

* <code>-o</code> tells where to write the resulting header

* <code>-o</code> tells where to write the resulting header

Once <code>parasite.h</code> file is ready, it should be included into the infecting program source code to be compiled with it.

Once <code>parasite.h</code> file is ready, it should be included into the infecting program source code to be compiled with it.

First, the <code>ctl</code> should be configured with the blob information. For that,

First, the <code>ctl</code> should be configured with the blob information. For that,

you should call <code>''PREFIX''_setup_c_header()</code> function,

you should call <code>''PREFIX''_setup_c_header()</code> function

where <code>''PREFIX''</code> is the same as the argument given to

with <code>ctl</code> as an argument. Here <code>''PREFIX''</code>

<code>-p</code> option to <code>compel hgen</code>.

is the same as the argument given to <code>-p</code> option

to <code>compel hgen</code>, and if not given, it is derived

(in the above example it's <code>parasite</code>).

Second, when infecting a parasite one should specify the amount of threads it will mess with (1, if only the thread leader will be accessed) and the maximum size of the memory area shared between infecting task and parasite used for arguments/result passing.

Second, when infecting a parasite one should specify the amount of threads it will mess with (1, if only the thread leader will be accessed) and the maximum size of the memory area shared between infecting task and parasite used for arguments/result passing.

* [[Compel/Usage_scenarios]]

* [[Compel/Usage_scenarios]]

* [[Compel plugins]]

* [[Compel plugins]]

* Examples of working code available [https://github.com/xemul/criu/tree/criu-dev/compel/test on github] <ref>Clone the repo, build the project by running <code>make</code>, then go to <code>compel/test/$test_name</code> directory and run <code>make</code> there. Running <code>spy</code> bynary runs the example. Then -- RTFS or talk to us on [https://lists.openvz.org/mailman/listinfo/criu criu@openvz.org] :)</ref>

* Examples of working code available [https://github.com/checkpoint-restore/criu/tree/criu-dev/compel/test on github] <ref>Clone the repo, build the project by running <code>make</code>, then go to <code>compel/test/$test_name</code> directory and run <code>make</code> there. Running <code>spy</code> bynary runs the example. Then -- RTFS or talk to us on [https://lists.openvz.org/mailman/listinfo/criu criu@openvz.org] :)</ref>

* Info about CRIU [[code blobs]] in which the same technology is used

* Info about CRIU [[code blobs]] in which the same technology is used

<references/>

<references/>

[[Category:Compel]]

[[Category:Compel]]