From: Jeff Layton <jlayton@kernel.org>
To: corbet@lwn.net
Cc: viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: [PATCH] Documentation: atomic_open called with shared lock on non-O_CREAT open
Date: Wed, 30 Oct 2019 06:46:54 -0400 [thread overview]
Message-ID: <20191030104654.6315-1-jlayton@kernel.org> (raw)
The exclusive lock is only held when O_CREAT is set.
Signed-off-by: Jeff Layton <jlayton@kernel.org>
---
Documentation/filesystems/locking.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/filesystems/locking.rst b/Documentation/filesystems/locking.rst
index fc3a0704553c..5057e4d9dcd1 100644
--- a/Documentation/filesystems/locking.rst
+++ b/Documentation/filesystems/locking.rst
@@ -105,7 +105,7 @@ getattr: no
listxattr: no
fiemap: no
update_time: no
-atomic_open: exclusive
+atomic_open: shared (exclusive if O_CREAT is set in open flags)
tmpfile: no
============ =============================================
--
2.21.0
next reply other threads:[~2019-10-30 10:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 10:46 Jeff Layton [this message]
2019-11-07 20:03 ` [PATCH] Documentation: atomic_open called with shared lock on non-O_CREAT open Jonathan Corbet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191030104654.6315-1-jlayton@kernel.org \
--to=jlayton@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).