lkml.org 
[lkml]   [2020]   [Jul]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 04/10] Documentation: filesystems: directory-locking: drop doubled word
    Date
    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
    ---
    Documentation/filesystems/directory-locking.rst | 4 ++--
    1 file changed, 2 insertions(+), 2 deletions(-)

    --- linux-next-20200701.orig/Documentation/filesystems/directory-locking.rst
    +++ linux-next-20200701/Documentation/filesystems/directory-locking.rst
    @@ -28,7 +28,7 @@ RENAME_EXCHANGE in flags argument) lock
    if the target already exists, lock it. If the source is a non-directory,
    lock it. If we need to lock both, lock them in inode pointer order.
    Then call the method. All locks are exclusive.
    -NB: we might get away with locking the the source (and target in exchange
    +NB: we might get away with locking the source (and target in exchange
    case) shared.

    5) link creation. Locking rules:
    @@ -56,7 +56,7 @@ rules:
    * call the method.

    All ->i_rwsem are taken exclusive. Again, we might get away with locking
    -the the source (and target in exchange case) shared.
    +the source (and target in exchange case) shared.

    The rules above obviously guarantee that all directories that are going to be
    read, modified or removed by method will be locked by caller.
    \
     
     \ /
      Last update: 2020-07-03 23:44    [W:4.602 / U:0.244 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site