Dmitry Safonov

Sure, as per my understanding of this: https://elixir.bootlin.com/linux/latest/source/arch/x86/mm/mmap.c#L194 It should be pretty easy. As CRIU restores mappings with MAP_FIXED, there shouldn't be many 5level-related issues. Probably, it'll be quite invisible...

I guess, there are still two issues I see: 1. `bootstrap_len` is a continuous block so we might fail to find this large amount for restorer - may be worth...

@avagin ping? :)

Probably, some of the files you've added have executable bit set?

> flog/include/compiler.h → criu/include/compiler.h Do you need this? I don't see anything new there from `git diff flog/include/compiler.h include/common/compiler.h`

Looking at the end result, I have some questions: 1. You don't integrate it with parasite/restorer as I can see, right? Is it planned? How do they work right now:...

Please, sign your work by adding `Signed-off-by: ...` to your commit message.

https://github.com/checkpoint-restore/criu/commit/2fdc09499d9df9c9e61d53cf0c121e3338538a8f#diff-53c8fb3b0e70ae163cfa6b9e86a4ac4ce339d505b99bfbb764a93cb425e4b8e6R235 (patches are welcome)

Hm, this seems like a workaround for a specific environment setup, rather than for a kernel code. Unsure if this should be hardcoded like this. Maybe an option in `criu.config`?...

You keep adding `Change-Id: Ia8956063cdc130650cfcde86851ee6a14331f2c2` that pollute git logs and don't provide anything outside your company. Clean these up, please.