diff options
| author | Jeff Layton <jlayton@redhat.com> | 2014-02-03 18:13:06 +0100 |
|---|---|---|
| committer | Jeff Layton <jlayton@redhat.com> | 2014-03-31 14:24:42 +0200 |
| commit | 46dad7603f21d64207820580c0bafd47934686d4 (patch) | |
| tree | bccde6816702fe891cd69b81337db9ffbf320d61 /fs/locks.c | |
| parent | locks: close potential race between setlease and open (diff) | |
| download | linux-46dad7603f21d64207820580c0bafd47934686d4.tar.xz linux-46dad7603f21d64207820580c0bafd47934686d4.zip | |
locks: clean up comment typo
Acked-by: J. Bruce Fields <bfields@fieldses.org>
Signed-off-by: Jeff Layton <jlayton@redhat.com>
Diffstat (limited to 'fs/locks.c')
| -rw-r--r-- | fs/locks.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/locks.c b/fs/locks.c index 2cfeea622f28..5e28612120c2 100644 --- a/fs/locks.c +++ b/fs/locks.c @@ -581,7 +581,7 @@ static void locks_delete_block(struct file_lock *waiter) * it seems like the reasonable thing to do. * * Must be called with both the i_lock and blocked_lock_lock held. The fl_block - * list itself is protected by the file_lock_list, but by ensuring that the + * list itself is protected by the blocked_lock_lock, but by ensuring that the * i_lock is also held on insertions we can avoid taking the blocked_lock_lock * in some cases when we see that the fl_block list is empty. */ |