diff options
| author | Tim Schumacher <timschumi@gmx.de> | 2022-05-13 12:20:57 +0200 |
|---|---|---|
| committer | Brian Gianforcaro <b.gianfo@gmail.com> | 2022-07-08 22:27:38 +0000 |
| commit | dc6016cd18deaeaf6121605540d876169475d491 (patch) | |
| tree | 0709f6dbc9d189fc107b4e47704dc6a3e389747e /Tests/AK/TestJSON.cpp | |
| parent | 7d3f71a6485791f9fb87621c5a15571889f6c687 (diff) | |
| download | serenity-dc6016cd18deaeaf6121605540d876169475d491.zip | |
Kernel: Don't fail on unlocking nonexistent file locks
I haven't found any POSIX specification on this, but the Linux kernel
appears to handle it like that.
This is required by QEMU, as it just bulk-unlocks all its file locking
bytes without checking first if they are held.
Diffstat (limited to 'Tests/AK/TestJSON.cpp')
0 files changed, 0 insertions, 0 deletions