- Newest
- Most votes
- Most comments
Hello Binoy,
Thank you for your post. Are you aware of the conditions in which this error is observed? Are requests made with the IO_URING helper APIs after the target has been unregistered?
I reviewed the changelog for the kernel version linux-signed-aws_5.19.0-1025.26 and I found one change that may be related:
https://launchpad.net/ubuntu/+source/linux-aws
-
Kinetic update: upstream stable patchset 2023-04-06 (LP: #2015511)
- aio: fix mremap after fork null-deref
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015511
You can find background details on this change in the Linux Kernel mailing list:
https://lkml.org/lkml/2022/11/4/1192
It may be necessary to inspect the specific actions taken by the liburing APIs to determine if the issue is indeed associated with the patch identified above.
Note that support for the default Ubuntu AMI is available directly from Canonical. I would encourage you to reach out to Canonical via their website (http://www.ubuntu.com/cloud/services) to report this issue, along with additional details such as replication steps.
Please let me know if you have any questions.
Thank you for the response and sorry for the delay. I was also reaching out to aws support. They recommended that i contact premium support.
What do you mean by deregistering target? Do you mean io_uring_register? I never used that API. However, i have used io_uring_register_files(). But I keep the files registered until the application ends and never deregister anything.
answered 3 years ago
Relevant content
asked 3 years ago
