From: Dharmendra Singh <dharamhans87@gmail.com>
To: miklos@szeredi.hu, vgoyal@redhat.com
Cc: Dharmendra Singh <dharamhans87@gmail.com>,
linux-fsdevel@vger.kernel.org, fuse-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, bschubert@ddn.com,
Dharmendra Singh <dsingh@ddn.com>
Subject: [PATCH v5 2/3] FUSE: Rename fuse_create_open() to fuse_atomic_common()
Date: Tue, 17 May 2022 15:37:43 +0530 [thread overview]
Message-ID: <20220517100744.26849-3-dharamhans87@gmail.com> (raw)
In-Reply-To: <20220517100744.26849-1-dharamhans87@gmail.com>
This patch just changes function name as it is used in next patch
to make code better readable.
Signed-off-by: Dharmendra Singh <dsingh@ddn.com>
---
fs/fuse/dir.c | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/fs/fuse/dir.c b/fs/fuse/dir.c
index ed9da8d6b57b..517c9add014d 100644
--- a/fs/fuse/dir.c
+++ b/fs/fuse/dir.c
@@ -521,9 +521,9 @@ static int get_security_context(struct dentry *entry, umode_t mode,
* If the filesystem doesn't support this, then fall back to separate
* 'mknod' + 'open' requests.
*/
-static int fuse_create_open(struct inode *dir, struct dentry *entry,
- struct file *file, unsigned int flags,
- umode_t mode, uint32_t opcode)
+static int fuse_atomic_common(struct inode *dir, struct dentry *entry,
+ struct file *file, unsigned int flags,
+ umode_t mode, uint32_t opcode)
{
int err;
struct inode *inode;
@@ -674,8 +674,8 @@ static int fuse_create_ext(struct inode *dir, struct dentry *entry,
if (fc->no_create_ext)
return -ENOSYS;
- err = fuse_create_open(dir, entry, file, flags, mode,
- FUSE_CREATE_EXT);
+ err = fuse_atomic_common(dir, entry, file, flags, mode,
+ FUSE_CREATE_EXT);
/* If ext create is not implemented then indicate in fc so that next
* request falls back to normal create instead of going into libufse and
* returning with -ENOSYS.
@@ -723,8 +723,8 @@ static int fuse_atomic_open(struct inode *dir, struct dentry *entry,
if (err == -ENOSYS)
goto lookup;
} else
- err = fuse_create_open(dir, entry, file, flags, mode,
- FUSE_CREATE);
+ err = fuse_atomic_common(dir, entry, file, flags, mode,
+ FUSE_CREATE);
if (err == -ENOSYS) {
fc->no_create = 1;
goto mknod;
--
2.17.1
next prev parent reply other threads:[~2022-05-17 10:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 10:07 [PATCH v5 0/3] FUSE: Implement atomic lookup + open/create Dharmendra Singh
2022-05-17 10:07 ` [PATCH v5 1/3] FUSE: Avoid lookups in fuse create Dharmendra Singh
2022-05-17 21:21 ` Vivek Goyal
2022-05-18 17:41 ` Vivek Goyal
2022-05-18 17:44 ` Vivek Goyal
2022-05-18 20:28 ` Bernd Schubert
2022-05-17 10:07 ` Dharmendra Singh [this message]
2022-05-17 10:07 ` [PATCH v5 3/3] FUSE: Implement atomic lookup + open Dharmendra Singh
2022-05-19 9:39 ` [PATCH v5 0/3] FUSE: Implement atomic lookup + open/create Miklos Szeredi
2022-05-19 13:13 ` Miklos Szeredi
2022-05-19 17:41 ` Bernd Schubert
2022-05-19 18:16 ` Miklos Szeredi
2022-05-19 20:47 ` [fuse-devel] " Bernd Schubert
2022-05-19 19:33 ` Vivek Goyal
2023-06-01 11:16 ` Bernd Schubert
2023-06-01 11:50 ` Miklos Szeredi
2023-06-01 12:01 ` Bernd Schubert
2023-06-01 12:18 ` Miklos Szeredi
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=20220517100744.26849-3-dharamhans87@gmail.com \
--to=dharamhans87@gmail.com \
--cc=bschubert@ddn.com \
--cc=dsingh@ddn.com \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=vgoyal@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.