Weijie Liu

Thanks! I also encountered this problem. The solution is really helpful! And remember to re-build the app before you run it .

It's weird that according to the [code](https://github.com/occlum/occlum/blob/master/src/libos/src/ipc/shm.rs#L358), the size should be returned correctly...

This "segment size was incorrect" error also occurs when shmaddr is a page-aligned address.

Meanwhile, the maximum nesting level allowed within an epoll set is 5; otherwise, `epoll_ctl` will fail and return `EINVAL`. When already nested five levels deep, the expected behavior should return...

When a fd refers to an epoll instance and the EPOLL_CTL_ADD operation results in epoll instances monitoring each other (using `epoll_ctl(..., EPOLL_CTL_ADD, ...)`), creating a nesting loop, the expected behavior...

Thanks for the info. Yes, this issue also occurs in the `mremap` syscall. Employing `mremap` to reallocate an existing mapped memory region (memsize) according to a new size ought to...

> Thank you for reporting this issue. This is a known issue. We will add permission checks on all memory-related syscalls. And the issue also occurs in the `mmap` syscall...

You can check on #855 about this issue. And any input will be appreciated!

This PR has been reviewed line by line by me and @grief8 .

> I'm considering renaming `struct Path` to `struct DentryMnt` since this structure is at the VFS layer and can uniquely determine the location in a directory tree. I also think...