Linus Torvalds writes: (Summary) wrote:
I'm going to assume I get this for 4.17 from the security tree. And the only other security module that even registers this is loadpin, and again it just seems to check things like "on the right filesystem" that aren't actually impacted by write access (in fact, the documented reason is to check that it's a read-only filesystem so that write access is simply _irrelevant_).
that write access is simply _irrelevant_).
So this issue seems to be mainly a cleanliness thing, not an actual bug.
[...]
contents could change between the two.I'm going to assume I get this for 4.17 from the security tree. And the only other security module that even registers this is loadpin, and again it just seems to check things like "on the right filesystem" that aren't actually impacted by write access (in fact, the documented reason is to check that it's a read-only filesystem so that write access is simply _irrelevant_).
that write access is simply _irrelevant_).
So this issue seems to be mainly a cleanliness thing, not an actual bug.