diff options
author | NeilBrown <neilb@suse.com> | 2018-11-30 10:04:08 +1100 |
---|---|---|
committer | Jeff Layton <jlayton@kernel.org> | 2018-11-30 11:26:12 -0500 |
commit | ada5c1da8660ecae24b3e75c18ee77d79e099fee (patch) | |
tree | c1579a9a4924fa11b6fc49cc9bdb7e5f3e59aae4 /firmware | |
parent | ccda4af0f4b92f7b4c308d3acc262f4a7e3affad (diff) | |
download | linux-stable-ada5c1da8660ecae24b3e75c18ee77d79e099fee.tar.gz linux-stable-ada5c1da8660ecae24b3e75c18ee77d79e099fee.tar.bz2 linux-stable-ada5c1da8660ecae24b3e75c18ee77d79e099fee.zip |
fs/locks: rename some lists and pointers.
struct file lock contains an 'fl_next' pointer which
is used to point to the lock that this request is blocked
waiting for. So rename it to fl_blocker.
The fl_blocked list_head in an active lock is the head of a list of
blocked requests. In a request it is a node in that list.
These are two distinct uses, so replace with two list_heads
with different names.
fl_blocked_requests is the head of a list of blocked requests
fl_blocked_member is a node in a member of that list.
The two different list_heads are never used at the same time, but that
will change in a future patch.
Note that a tracepoint is changed to report fl_blocker instead
of fl_next.
Signed-off-by: NeilBrown <neilb@suse.com>
Reviewed-by: J. Bruce Fields <bfields@redhat.com>
Signed-off-by: Jeff Layton <jlayton@kernel.org>
Diffstat (limited to 'firmware')
0 files changed, 0 insertions, 0 deletions