[Feature request] Open device read-only about libmetal

[arnopo]

Are you talking about metal_device_open?
Could you please explain your use case so that we understand the need?

[anon00000000]

Hello and yes. Use case is just making sure it is never written to even in case of program malfunction; a bit like using the correct mode in open(3) even when RDWR would work for every case.
We already cast all of our metal_io_virt pointers to const pointers, but that's tacit security, OS enforced protection like mprotect is a bit stronger.

[arnopo]

I suppose that your need is for Linux user space, right?
I think that the best solution to move forward is that you send a PR (even if it is an RFC), that implements what you would expect.
This would be a better base for discussions.

[anon00000000]

I guess so

[github-actions]

This issue has been marked as a stale issue because it has been open (more than) 45 days with no activity.