We completed a test this morning with the modified pigpio library and
verified our applications can now read the GPIO signals once we removed
the PROT_EXEC flags from the library init code.
We will pursue getting a change in with the pigpio library separately.
--
You received this bug
We are going to try editing the pigpio library and rebuilding it and
seeing if it works. There doesn't appear to be a clear requirement for
pigpio to rely on PROT_EXEC and it has been removed in the past.
Conversation about this is happening here:
https://github.com/joan2937/pigpio/issues/375
This is not a kernel problem. The problem is that the pigpio library is
trying to mmap the GPIOs with PROT_EXEC which is a security risk. In
Focal /dev is mounted with the noexec flag so that's no longer possible.
They could patch the pigpio library to remove the PROT_EXEC flag from
the mmap call
This is an important issue blocking the project. Can we please set the
importance and assign this? Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889926
Title:
Can't access gpio mapped
I've confirmed that 5.4 gives 'permission denied' and 5.3 seems to work
fine. I suspect that this is due to the lockdown patches in 5.4.
** Changed in: linux-raspi (Ubuntu Focal)
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Also affects: linux-raspi (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-raspi (Ubuntu)
Status: New => Invalid
** Changed in: linux-raspi (Ubuntu Focal)
Status: New => Triaged
--
You received this bug notification because you are a member of
