The constant values (#define LOCKDIR ...) hasn't been touched in these patches, meaning that it was already like that before this SRU.
With that being said, the LOCKDIR location isn't a problem, so IMHO, there is no need for the LOCKDIR in Trusty to move to "/run" if it doesn't create a problem.
The real issue here is that if ebtables crashes or is killed it leave a stale lock file behind which then blocks new ebtables from running.
This SRU is precisely fixing this issue by improving the locking mechanism.
@szilard,
The constant values (#define LOCKDIR ...) hasn't been touched in these patches, meaning that it was already like that before this SRU.
With that being said, the LOCKDIR location isn't a problem, so IMHO, there is no need for the LOCKDIR in Trusty to move to "/run" if it doesn't create a problem.
The real issue here is that if ebtables crashes or is killed it leave a stale lock file behind which then blocks new ebtables from running.
This SRU is precisely fixing this issue by improving the locking mechanism.
- Eric