> As a side note this is where I should also note the *current* LSM hooks > are racy as is. Suppose you can stat a particular file now, but a chown > to 1234 means you can't. Then your stat call can race against chown + > other ops. You can end up in a state where LSMs gave a green light and > only then the state changed to one you are not allowed to look at. This Fwiw, we've discussed this before. And my opinion is that we should absolute not care about this. I have no interest in complicating path lookup or any codepath to make these hooks less racy. This raciness they have to deal with. This is not a comment on your patch but just that the raciness of security hooks is not a problem we should care to solve imho. If we go down that road we'll all slowly go insane trying to give state change guarantees to layers that hook into the VFS in really odd locations.
