[CRIU] GSoC 2021

Radostin Stoyanov rstoyanov1 at gmail.com
Tue May 18 18:22:36 MSK 2021


On 18/05/2021 11:43, Zeyad Yasser wrote:

> Hi Everyone,
>
> My name is Zeyad @zeyadyasser, a CS undergrad at Cairo University. I
> am very
> grateful to have been accepted this year in CRIU. I will be working
> on "Using eBPF to
> <https://criu.org/Google_Summer_of_Code_Ideas#Use_eBPF_to_lock_and_unlock_the_network>
> lock/unlock the network"
> <https://criu.org/Google_Summer_of_Code_Ideas#Use_eBPF_to_lock_and_unlock_the_network> under
> the mentorship of @rst0git.
>
> I took interest in CRIU over the last year and have been tinkering
> with the code base
> ever since. I learned a lot about Linux internals because of CRIU and
> I am really
> grateful for the help and feedback I got from the maintainers. I was
> able to make
> some contributions to CRIU and P.Haul during this time.
>
> I divided the project into phases:
>
>     - Learn RTNETLINK & eBPF assembly
>     - Design execution flow in CRIU
>     - Implement network-wide locking/unlocking
>     - Implement per-socket locking/unlocking
>     - Testing
>     - Documentation
>
> The details of the approach and phases could be found in my proposal
> <https://docs.google.com/document/d/10tciq4ErZwphUIWkgj-IlHFBNZdHqBfjwn74l2V7tRM/edit?usp=sharing>.
>
> I believe I should start with learning how to use the RTNETLINK
> interface to load traffic
> control BPF programs as this is essential to all other phases of the
> project.
>
> I was wondering where I should document my progress? In the mailing
> list? Gitter? My blog?
>
Welcome! I am looking forward to your contributions.

You can use GitHub pull requests to document your progress, as this is
the preferred way to contribute to CRIU, but If you have any questions
you can always reach out in Gitter or open a GitHub issue for discussions.

Radostin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/criu/attachments/20210518/a50d2bb3/attachment.html>


More information about the CRIU mailing list