diff options
| author |   Pavel Begunkov <asml.silence@gmail.com> | 2019-07-24 20:16:31 +0300 |
|---|---|---|
| committer |   Jeff Layton <jlayton@kernel.org> | 2019-07-25 07:49:44 -0400 |
| commit | 43e4cb942e88e756b41ea4d30249a47973880508 (patch) | |
| tree | 3e11e0e5ae91bde90b618eb0385c2dbc55ad7956 /fs/drop_caches.c | |
| parent | locks: revise generic_add_lease tracepoint (diff) | |
| download | linux-dev-43e4cb942e88e756b41ea4d30249a47973880508.tar.xz linux-dev-43e4cb942e88e756b41ea4d30249a47973880508.zip | |
locks: Fix procfs output for file leases
Since commit 778fc546f749c588aa2f ("locks: fix tracking of inprogress
lease breaks"), leases break don't change @fl_type but modifies
@fl_flags. However, procfs's part haven't been updated.
Previously, for a breaking lease the target type was printed (see
target_leasetype()), as returns fcntl(F_GETLEASE). But now it's always
"READ", as F_UNLCK no longer means "breaking". Unlike the previous
one, this behaviour don't provide a complete description of the lease.
There are /proc/pid/fdinfo/ outputs for a lease (the same for READ and
WRITE) breaked by O_WRONLY.
-- before:
lock: 1: LEASE BREAKING READ 2558 08:03:815793 0 EOF
-- after:
lock: 1: LEASE BREAKING UNLCK 2558 08:03:815793 0 EOF
Signed-off-by: Pavel Begunkov <asml.silence@gmail.com>
Signed-off-by: Jeff Layton <jlayton@kernel.org>
Diffstat (limited to 'fs/drop_caches.c')
0 files changed, 0 insertions, 0 deletions