From: Paul Aurich <paul@darkrain42.org>
To: Shyam Prasad N <nspmangalore@gmail.com>
Cc: Steve French <smfrench@gmail.com>,
Bharath SM <bharathsm.hsk@gmail.com>,
linux-cifs@vger.kernel.org, sfrench@samba.org, pc@manguebit.com,
sprasad@microsoft.com, tom@talpey.com, ronniesahlberg@gmail.com,
Bharath SM <bharathsm@microsoft.com>
Subject: Re: [PATCH] smb: enable reuse of deferred file handles for write operations
Date: Thu, 19 Dec 2024 14:47:41 -0800 [thread overview]
Message-ID: <Z2SijUfZWp37R2Do@haley.home.arpa> (raw)
In-Reply-To: <CANT5p=rYjgbteSBRuZFfXYwC-g6QLMG20250RzO9Es8GZPeL2g@mail.gmail.com>
On 2024-12-19 15:03:48 +0530, Shyam Prasad N wrote:
>On Tue, Dec 17, 2024 at 2:22 AM Steve French <smfrench@gmail.com> wrote:
>>
>> merged into cifs-2.6.git for-next pending review and more testing
>>
>> On Mon, Dec 16, 2024 at 12:36 PM Bharath SM <bharathsm.hsk@gmail.com> wrote:
>> >
>> > Previously, deferred file handles were reused only for read
>> > operations, this commit extends to reusing deferred handles
>> > for write operations.
>> >
>> > Signed-off-by: Bharath SM <bharathsm@microsoft.com>
>> > ---
>> > fs/smb/client/file.c | 6 +++++-
>> > 1 file changed, 5 insertions(+), 1 deletion(-)
>> >
>> > diff --git a/fs/smb/client/file.c b/fs/smb/client/file.c
>> > index a58a3333ecc3..98deff1de74c 100644
>> > --- a/fs/smb/client/file.c
>> > +++ b/fs/smb/client/file.c
>> > @@ -990,7 +990,11 @@ int cifs_open(struct inode *inode, struct file *file)
>> > }
>> >
>> > /* Get the cached handle as SMB2 close is deferred */
>> > - rc = cifs_get_readable_path(tcon, full_path, &cfile);
>> > + if (OPEN_FMODE(file->f_flags) & FMODE_WRITE) {
>> > + rc = cifs_get_writable_path(tcon, full_path, FIND_WR_ANY, &cfile);
>
>Wondering if FIND_WR_ANY is okay for all use cases?
>Specifically, I'm checking where FIND_WR_FSUID_ONLY is relevant.
>@Steve French Is this for multiuser mounts? I don't think so, since
>multiuser mounts come with their own tcon, and we search writable
>files in our tcon's open list.
I think this should be FIND_WR_FSUID_ONLY, yeah. (IMHO, that should be the
default, and FIND_WR_ANY should be renamed something indicating it should only
be used in specific situations and it's probably not what the caller wants.)
I have a series I need to resurrect and polish that fixes a few problems along
these lines, but it doesn't touch the 'writable file' path.
>> > + } else {
>> > + rc = cifs_get_readable_path(tcon, full_path, &cfile);
>> > + }
>> > if (rc == 0) {
>> > if (file->f_flags == cfile->f_flags) {
>> > file->private_data = cfile;
>> > --
>> > 2.43.0
>> >
>> >
>>
>>
>> --
>> Thanks,
>>
>> Steve
>>
>Other than that one thing to look at, the changes look good to me.
>
>--
>Regards,
>Shyam
~Paul
next prev parent reply other threads:[~2024-12-19 22:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 18:31 [PATCH] smb: enable reuse of deferred file handles for write operations Bharath SM
2024-12-16 20:43 ` Steve French
2024-12-19 9:33 ` Shyam Prasad N
2024-12-19 22:47 ` Paul Aurich [this message]
2024-12-23 8:12 ` Bharath SM
2024-12-23 18:48 ` Steve French
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=Z2SijUfZWp37R2Do@haley.home.arpa \
--to=paul@darkrain42.org \
--cc=bharathsm.hsk@gmail.com \
--cc=bharathsm@microsoft.com \
--cc=linux-cifs@vger.kernel.org \
--cc=nspmangalore@gmail.com \
--cc=pc@manguebit.com \
--cc=ronniesahlberg@gmail.com \
--cc=sfrench@samba.org \
--cc=smfrench@gmail.com \
--cc=sprasad@microsoft.com \
--cc=tom@talpey.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.