diff options
| author | Jeff Layton <jlayton@kernel.org> | 2021-09-10 15:36:29 -0400 |
|---|---|---|
| committer | Jeff Layton <jlayton@kernel.org> | 2021-09-10 16:21:44 -0400 |
| commit | 90f7d7a0d0d68623b5f7df5621a8d54d9518fcc4 (patch) | |
| tree | 45d9848be89c64360b82aa49fbb19af46eb46164 /crypto/geniv.c | |
| parent | bf9f243f23e6623f310ba03fbb14e10ec3a61290 (diff) | |
| download | linux-stable-90f7d7a0d0d68623b5f7df5621a8d54d9518fcc4.tar.gz linux-stable-90f7d7a0d0d68623b5f7df5621a8d54d9518fcc4.tar.bz2 linux-stable-90f7d7a0d0d68623b5f7df5621a8d54d9518fcc4.zip | |
locks: remove LOCK_MAND flock lock support
As best I can tell, the logic for these has been broken for a long time
(at least before the move to git), such that they never conflict with
anything. Also, nothing checks for these flags and prevented opens or
read/write behavior on the files. They don't seem to do anything.
Given that, we can rip these symbols out of the kernel, and just make
flock(2) return 0 when LOCK_MAND is set in order to preserve existing
behavior.
Cc: Matthew Wilcox <willy@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>
Signed-off-by: Jeff Layton <jlayton@kernel.org>
Diffstat (limited to 'crypto/geniv.c')
0 files changed, 0 insertions, 0 deletions