Documentation: filesystems: directory-locking: drop doubled word

Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

kernel os linux

Drop the doubled word "the".

Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org
Cc: Alexander Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org
Link: https://lore.kernel.org/r/20200703214325.31036-5-rdunlap@infradead.org
Signed-off-by: Jonathan Corbet <corbet@lwn.net>

authored by

Randy Dunlap and committed by

Jonathan Corbet 5 years ago 2f32295c 58c8e97d

+2 -2

1 changed file

expand all

Documentation

filesystems

directory-locking.rst

+2 -2

Documentation/filesystems/directory-locking.rst

··· 28 28 if the target already exists, lock it. If the source is a non-directory, 29 29 lock it. If we need to lock both, lock them in inode pointer order. 30 30 Then call the method. All locks are exclusive. 31 - NB: we might get away with locking the the source (and target in exchange 31 + NB: we might get away with locking the source (and target in exchange 32 32 case) shared. 33 33 34 34 5) link creation. Locking rules: ··· 56 56 * call the method. 57 57 58 58 All ->i_rwsem are taken exclusive. Again, we might get away with locking 59 - the the source (and target in exchange case) shared. 59 + the source (and target in exchange case) shared. 60 60 61 61 The rules above obviously guarantee that all directories that are going to be 62 62 read, modified or removed by method will be locked by caller.