Name	Name	Last commit message	Last commit date
parent directory ..
Dockerfile	Dockerfile
INFO	INFO
README.md	README.md
Results.xlsx	Results.xlsx
cve-data.json	cve-data.json
driver.py	driver.py
main-data.json	main-data.json

Experiment Replication

FixMorph successfully generates correct transformation for 75.1% of the subjects in our data-set which are curated from backported patches in the Linux Kernel project.

In our replication package, we include scripts to reproduce the experiment using fixmorph. This directory includes scripts and Dockerfile to re-create the experiment setup and reproduce the evaluation results.

Dockerhub Repo: https://hub.docker.com/repository/docker/rshariffdeen/fixmorph

Getting Started

Hardware Requirements

All experiments were conducted using Ubuntu 18.04 operating system on a Dell Power Edge R530 Intel(R) Xeon(R) CPU E5-2660 processor and 64GB RAM.

Docker Preliminaries

Ensure you have docker installed. See: https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-on-ubuntu-16-04
Ensure you have added yourself to the docker group: sudo usermod -a -G docker <username>. You will need to log back in to see the permissions take effect.

Building the environment

Please note that the environment to run the experiments requires building 2 docker images:

Docker image for FixMorph tool and its dependencies (to build FixMorph)
Docker image for Linux kernel project build environment and its dependencies (to compile Linux kernel modules)

Setup environment can be built using the Dockerfile provided within, which will encompass the dependencies, configurations and setup scripts. Use the following command:

git clone https://github.com/rshariffdeen/FixMorph.git

# building docker image for FixMorph
cd /FixMorph
docker build -t rshariffdeen/fixmorph:16.04 .

# building docker image for Linux experiments
cd /FixMorph/experiments/ISSTA21
docker build -t rshariffdeen/fixmorph:issta21 .

Note that the build process can be time-consuming, hence you can using the following command to download pre-built Docker image from following repository Dockerhub Repo: https://hub.docker.com/repository/docker/rshariffdeen/fixmorph

docker pull rshariffdeen/fixmorph:issta21

Having the image, you can now start a Docker container. Note: please make sure to use the correct image which has the dependencies installed for Linux kernel (i.e. rshariffdeen/fixmorph:issta21)

docker run --name FixMorph -it rshariffdeen/fixmorph:issta21 bash

Test Input Files

We will first run a test example to verify that FixMorph is working in the given environment, for this purpose we will use the test-case provided in the directory 'tests/update/assignment'. In this example we provide three C source files and their corresponding Makefiles, in addition we also provide the configuration file for FixMorph.

/FixMorph/tests/update/assignment/repair.conf is the FixMorph configuration file.
/FixMorph/tests/update/assignment/PA lists the source files for pre-transform version of the reference version
/FixMorph/tests/update/assignment/PB lists the source files for post-transform version of the reference version
/FixMorph/tests/update/assignment/PC lists the source files for target version

Test Run

You can check if everything is working well by running the above test-case from our test-suite.

python3.7 FixMorph.py --conf=tests/update/assignment/repair.conf

This example test-case illustrates a change in a sorting logic. The patch updates the field use of the sorting logic from 'rank' to entity 'id'. We use FixMorph to learn the transformation rule and apply it to another similar but different version.

FixMorph Output

The output message at the end of the execution should look similar to the following:

Initialization: 0.000 minutes
Build Analysis: 0.000 minutes
Diff Analysis: 0.001 minutes
Clone Analysis: 0.005 minutes
Slicing: 0.000 minutes
AST Analysis: 0.001 minutes
Map Generation: 0.011 minutes
Translation: 0.002 minutes
Evolution: 0.004 minutes
Transplantation: 0.004 minutes
Verification: 0.002 minutes
Comparison: 0.000 minutes
Summarizing: 0.002 minutes

FixMorph finished successfully after 0.032 minutes

Analysing Results

FixMorph was able to successfully generate an updated version of the target program from the transformation learnt from the reference program. During this process FixMorph produces several files and we will analyse each below:

/FixMorph/logs/TAG_ID directory stores all logs, the "TAG_ID" should be specified in the configuration file
- log-latest: this is the main application log which captures each step of the program transformation
- log-error: this log captures any errors (if observed), which can be use for debugging purpose
- log-make: this log captures the output of the build process of each program
/FixMorph/output/TAG_ID directory stores all artefacts generated for the transformation, the "TAG_ID" should be specified in the configuration file
- orig-diff: this file captures the transformation in the reference program
- transplant-diff: this file captures the transformation applied to the target program
- port-diff: this file captures the transformation done in manual (comparison phase will run only if an additional version of target program "Pe" is provided in configuration)
- vector-map: this file shows the mapping for the function/source files
- namespace-map-global: this file shows the generated global mapping for each function/slice mapped

To better explore the final outcome, please check the FixMorph output directory which is in /FixMorph/output/<tag_id> (for this example the tag_id defined in the configuration file is 'update-test') i.e. /FixMorph/output/update-test Similarly, the logs are also stored in /FixMorph/logs/<tag_id>.

For more examples refer this guide.

Running Experiments

Following details how to run the scripts and the tool to replicate the results of our experiments. Once you build the docker image, you spin up a container as mentioned above.

Inside the container the following directories/files will be used

/FixMorph - this is the tool directory
/experiments/ISSTA21 - all experiment setups will be deployed in this directory
/experiments/ISSTA21/main-data.json - this contains the meta-data for the main experiment of (350 commits)
/experiments/ISSTA21/cve-data.json - this contains the meta-data for the cve-fixes

In /experiments/ISSTA21 directory a python driver is provided to run all experiments. You can run all the experiments using the following command

python3.7 driver.py --data=[cve-data.json/main-data.json]

You can specify the driver to setup the environment and manually run the tool later by using following command, which will setup the experiment data in /data directory.

python3.7 driver.py --data=[cve-data.json/main-data.json] --only-setup

You can also select a single test-case you want to replicate by running the following command, where the bug ID is the id specified in our benchmark.

python3.7 driver.py --data=[cve-data.json/main-data.json] --bug-id=BUG_ID

Alternatively, you can run the experiment manually (after setting up)

python3.7 FixMorph.py --conf=/path/to/configuration
python3.7 FixMorph.py --conf=/data/backport/linux/1/repair.conf
python3.7 FixMorph.py --conf=/data/backport/linux-cve/1/repair.conf

Running experiment #238 (Patch Type-3)

Lets run one of the experiments (Bug-ID 238) in our data-set using the following command. The general experiment timeout is set to 1hr. [Note: to stop a run, please use CTRL+C]

Step 1 - Setting up the experiment

First, we need to prepare the experiment by setting up the source directories. We use the following command:

cd /FixMorph/experiments/ISSTA21
python3.7 driver.py --data=main-data.json --only-setup --bug-id=238

Once the setup is completed, you can verify the setup is located at /data/backport/linux/BUG_ID

Step 2 - Running FixMorph

Next step is to invoke FixMorph with the experiment configuration, using the following command:

cd /FixMorph
python3.7 FixMorph.py --conf=/data/backport/linux/238/repair.conf

The transformation should be completed in ~10 minutes.

Step 3 - Analysing Results

You can observe the transformation from the following artefacts, which shows that FixMorph generated a semantically equivalent transformation compared to the patch that developer manually ported.

Original Patch

430a431
> 		if ((status != -ENOENT) || (urb->actual_length == 0))

Ported Patch (Manual Dev)

429a430
> 		if ((urb->status != -ENOENT) || (urb->actual_length == 0))

Transplanted Patch (FixMorph Generated)

413a414,415
>  int status = urb->status; 

430c432,434
< 		return;
---
> if ((status != -ENOENT) || (urb->actual_length == 0))
> 			return;

General Notes

The same steps need to be performed for all other subjects. The experimental results can differ in terms of timeout for different computation power TIMEOUT is set to 1hr by default, which can be modified passing the argument "--time=TIME" as shown in below command. In addition, you can specify which mode of transformation to use from

0: FixMorph
1: Linux Patch No-Context
2: Linux Patch using Context
3: SYDIT

cd /FixMorph
python3.7 FixMorph.py --conf=/data/backport/linux/238/repair.conf --time=TIME --mode=MODE_NUMBER

Additional Files

Please find below files useful for the replication of the experiments

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

ISSTA21

ISSTA21

README.md

Experiment Replication

Getting Started

Hardware Requirements

Docker Preliminaries

Building the environment

Test Input Files

Test Run

FixMorph Output

Analysing Results

Running Experiments

Running experiment #238 (Patch Type-3)

Step 1 - Setting up the experiment

Step 2 - Running FixMorph

Step 3 - Analysing Results

Original Patch

Ported Patch (Manual Dev)

Transplanted Patch (FixMorph Generated)

General Notes

Additional Files

Additional Links

Files

ISSTA21

Directory actions

More options

Directory actions

More options

Latest commit

History

ISSTA21

Folders and files

parent directory

README.md

Experiment Replication

Getting Started

Hardware Requirements

Docker Preliminaries

Building the environment

Test Input Files

Test Run

FixMorph Output

Analysing Results

Running Experiments

Running experiment #238 (Patch Type-3)

Step 1 - Setting up the experiment

Step 2 - Running FixMorph

Step 3 - Analysing Results

Original Patch

Ported Patch (Manual Dev)

Transplanted Patch (FixMorph Generated)

General Notes

Additional Files

Additional Links