clinuxlockingfile-locking

linux mandatory locking for file locking

I want to test mandatory locking in linux (Ubuntu 22.04.2 LTS) and I do the following steps

1- mount /dev/vgg1/lvv11 /u03 -o mand

2- chmod g+s /u03/datafile.dbf

3- chmod g-x /u03/datafile.dbf

and then execute the following code:

struct flock lock;
.....

fd = open("/u03/datafile.dbf", O_RDWR);
lock.l_type = F_WRLCK;
lock.l_start = 40;
lock.l_whence = SEEK_SET;
lock.l_len = 12;
err=fcntl(fd, F_SETLK, &lock);

but as the output of lslocks, as following , shows that means lock type is not mandatory!

COMMAND            PID  TYPE SIZE MODE  M START END PATH
llock           466440 POSIX 378B WRITE 0    40  51 /u03/datafile.dbf
cron            130607 FLOCK   7B WRITE 0     0   0 /run/crond.pid

what should I do to obtain mandatory lock?

Solution

  • This option, while it existed, required, as documented to mount the filesystem with -o mand and have setgid set and execute not set. OP did all of these.

    But still as documented this feature has always had issues on Linux. The very first paragraph (0.) on the documentation explains why mandatory locking should be avoided and gives an example outcome where after a process gained mandatory lock, data could still be written by an other process due to race conditions, breaking the contract of a mandatory lock.

    This feature (which appeared in kernel 4.5) was completely removed in kernel 5.15 with this commit:

    fs: remove mandatory file locking support

    We added CONFIG_MANDATORY_FILE_LOCKING in 2015, and soon after turned it off in Fedora and RHEL8. Several other distros have followed suit.

    [...]

    This patch rips out mandatory locking support wholesale from the kernel, along with the Kconfig option and the Documentation file. It also changes the mount code to ignore the "mand" mount option instead of erroring out, and to throw a big, ugly warning.

    Indeed, if you run dmesg after having used for the first time the -o mand option, you should get a big multi-line warning message telling support was removed.

    Example on a system using Linux 6.6.x that didn't use -o mand since boot:

    # mkdir /tmp/test
# mount -t tmpfs tmpfs -o mand /tmp/test
# dmesg | tail -n5
[1788215.604544] =======================================================
                 WARNING: The mand mount option has been deprecated and
                          and is ignored by this kernel. Remove the mand
                          option from the mount to silence this warning.
                 =======================================================

    So you have to run an older kernel with this feature enabled to get to use it. Examples of still (but not for long) supported Linux distributions with this feature enabled

    As written in commit, RHEL-like distributions dropped support early, so I don't expect any shipped kernels from them to have CONFIG_MANDATORY_FILE_LOCKING=y. Rolling-release-based distributions will have newer kernels so won't have this feature either.

    If your software was expected to rely on this feature on Linux, its code will have to be changed to not rely on it anymore.