On Wed, Jan 17, 2018 at 12:06:33PM +0100, Karel Zak wrote: > What about new flag (for the API) rather than try to be smart with the > current flags? But I have doubts that invest time to new mount(2) > features is a good idea. Would be nice, if we had any spare bits left... We could, in principle, turn #define MS_BIND 4096 #define MS_MOVE 8192 into #define MS_BIND 0x1000 #define MS_MOVE 0x2000 #define MS_SOMETHING 0x3000 seeing that they should never be used together, but... mount(2) doesn't reject MS_BIND|MS_MOVE and treats it as MS_BIND instead. _Probably_ nothing would care, but it risks breaking userland. We could use one of the internal-only bits for that instead, but they are also quietly ignored and not rejected, so that would have the same problem. mount(2) ABI sucks, film at 11...
