From: Bernd Schubert <bschubert@ddn.com>
To: linux-fsdevel@vger.kernel.org
Cc: bernd.schubert@fastmail.fm, fuse-devel@lists.sourceforge.net,
Bernd Schubert <bschubert@ddn.com>,
Miklos Szeredi <miklos@szeredi.hu>,
Dharmendra Singh <dsingh@ddn.com>
Subject: [PATCH 1/6] fuse: rename fuse_create_open
Date: Wed, 16 Aug 2023 16:33:08 +0200 [thread overview]
Message-ID: <20230816143313.2591328-2-bschubert@ddn.com> (raw)
In-Reply-To: <20230816143313.2591328-1-bschubert@ddn.com>
Just preparation work for atomic open.
Signed-off-by: Bernd Schubert <bschubert@ddn.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>
Cc: Dharmendra Singh <dsingh@ddn.com>
Cc: linux-fsdevel@vger.kernel.org
---
fs/fuse/dir.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/fs/fuse/dir.c b/fs/fuse/dir.c
index 35bc174f9ba2..6ffc573de470 100644
--- a/fs/fuse/dir.c
+++ b/fs/fuse/dir.c
@@ -613,7 +613,7 @@ static void free_ext_value(struct fuse_args *args)
* 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,
+static int _fuse_create_open(struct inode *dir, struct dentry *entry,
struct file *file, unsigned int flags,
umode_t mode, u32 opcode)
{
@@ -753,7 +753,7 @@ static int fuse_atomic_open(struct inode *dir, struct dentry *entry,
if (fc->no_create)
goto mknod;
- err = fuse_create_open(dir, entry, file, flags, mode, FUSE_CREATE);
+ err = _fuse_create_open(dir, entry, file, flags, mode, FUSE_CREATE);
if (err == -ENOSYS) {
fc->no_create = 1;
goto mknod;
@@ -879,7 +879,7 @@ static int fuse_tmpfile(struct mnt_idmap *idmap, struct inode *dir,
if (fc->no_tmpfile)
return -EOPNOTSUPP;
- err = fuse_create_open(dir, file->f_path.dentry, file, file->f_flags, mode, FUSE_TMPFILE);
+ err = _fuse_create_open(dir, file->f_path.dentry, file, file->f_flags, mode, FUSE_TMPFILE);
if (err == -ENOSYS) {
fc->no_tmpfile = 1;
err = -EOPNOTSUPP;
--
2.37.2
next prev parent reply other threads:[~2023-08-16 14:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 14:33 [PATCH v8 0/6] fuse: full atomic open and atomic-open-revalidate Bernd Schubert
2023-08-16 14:33 ` Bernd Schubert [this message]
2023-08-16 14:33 ` [PATCH 2/6] fuse: introduce atomic open Bernd Schubert
2023-08-16 14:33 ` [PATCH 3/6] [RFC] Allow atomic_open() on positive dentry Bernd Schubert
2023-08-16 15:25 ` Miklos Szeredi
2023-08-16 15:54 ` Bernd Schubert
2023-08-16 14:33 ` [PATCH 4/6] fuse: Revalidate positive entries in fuse_atomic_open Bernd Schubert
2023-08-16 14:33 ` [PATCH 5/6] fuse: revalidate Set DCACHE_ATOMIC_OPEN for cached dentries Bernd Schubert
2023-08-16 14:33 ` [PATCH 6/6] fuse: Avoid code duplication in atomic open Bernd Schubert
-- strict thread matches above, loose matches on Subject: below --
2023-08-11 18:37 [PATCH v7 0/6] fuse: full atomic open and atomic-open-revalidate Bernd Schubert
2023-08-11 18:37 ` [PATCH 1/6] fuse: rename fuse_create_open Bernd Schubert
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=20230816143313.2591328-2-bschubert@ddn.com \
--to=bschubert@ddn.com \
--cc=bernd.schubert@fastmail.fm \
--cc=dsingh@ddn.com \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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).