Re: GSoC 2026: Interest in Checkpointing of POSIX Message Queues

Hi Radostin,

Thank you so much for your response and for confirming the availability 
of the project!

I will make sure to CC both you and Pavel in all future communications.

I will start looking at August Fu's patches at 
https://github.com/yuntongf/criu/pull/1 to understand the work that has 
been done and what gaps remain.

Regarding the scope, I understand that the goal is to implement both the 
kernel side  interface for undestructive message peeking and the CRIU 
userspace implementation that uses it, with working tests demonstrating 
correctness before submitting the kernel patches upstream. I will 
structure my proposal around this two-phase approach.

I will share a draft proposal with you both before the deadline.
For now I have just one more question before I take a deeper dive into 
August Fu's patches.

1. For the kernel patch specifically, should I target the mqueue virtual 
filesystem in ipc/mqueue.c, and is the approach similar to the MSG_PEEK 
implementation for Unix sockets?

Thank you again.



On 3/5/26 15:28, Radostin Stoyanov wrote:
> Hi Boluwatife,
> 
> Thank you for reaching out!
> 
> On Thu, 5 Mar 2026 at 13:15, Boluwatife Honour 
> <[email protected] <mailto:[email protected]>> wrote:
> 
>     Hello Radostin👋,
> 
>     My name is Boluwatife and I am interested in applying for
>     the "Checkpointing of POSIX Message Queues" GSoC 2026
>     project with CRIU.
> 
>     I  already set up the development environment onmy OS
>     (Ubuntu 24.04), built CRIU v4.2 from source on the criu-dev
>     branch, and successfully performed checkpoint/restore of
>     a basic process.
> 
>     I have been studying the problem by reading the MSG_PEEK
>     commit linked on the ideas page, reading issue #2285, and
>     experimenting with POSIX message queues directly on my
>     system using mq_open, mq_send and mq_receive to understand
>     the mechanism I would need to support.
> 
> It sounds like you are doing the right thing.
> 
>     I have also reached out to Pavel a couple of days ago but
>     wanted to contact you as well since you are also listed
>     as a mentor for this project.
> 
> It would be good to CC both Pavel and myself so that we are both aware 
> of the discussions :)
> 
>     Before I start drafting my proposal I have a few questions:
> 
>     1. Is this project still available for GSoC 2026?
> 
> Yes, I would be happy to help with the application for GSoC.
> 
>     2. Does the scope include both the kernel-side interface
>         and the CRIU userspace implementation, or primarily
>         one of the two?
> 
> Ideally, we would demonstrate that the proposed changes work before we 
> ask the kernel community to merge them.
> 
>     3. Are there prior attempts or discussions beyond
>         issue #2285 I should study?
> 
> August Fu created a few patches last year (https://github.com/yuntongf/ 
> criu/pull/1 <https://github.com/yuntongf/criu/pull/1>) but they haven't 
> been reviewed.
> 
>     4. Would you be open to reviewing a draft proposal
>         before the March 31st deadline?
> 
> Yes, please share a draft of your proposal and we can review it.
> 
> Best wishes,
> Radostin
>