From: Namjae Jeon <linkinjeon@kernel.org>
To: atheik <atteh.mailbox@gmail.com>
Cc: linux-cifs@vger.kernel.org, Steve French <smfrench@gmail.com>,
Hyeoncheol Lee <hyc.lee@gmail.com>
Subject: Re: [PATCH v2 1/3] ksmbd: request update to stale share config
Date: Tue, 9 Aug 2022 09:38:20 +0900 [thread overview]
Message-ID: <CAKYAXd9CBR92ydiBj+1u7hEnmahOK9V4qorJVzO0D1+iXJ4qzQ@mail.gmail.com> (raw)
In-Reply-To: <20220808220216.17235-1-atteh.mailbox@gmail.com>
2022-08-09 7:02 GMT+09:00, atheik <atteh.mailbox@gmail.com>:
> ksmbd_share_config_get() retrieves the cached share config as long
> as there is at least one connection to the share. This is an issue when
> the user space utilities are used to update share configs. In that case
> there is a need to inform ksmbd that it should not use the cached share
> config for a new connection to the share. With these changes the tree
> connection flag KSMBD_TREE_CONN_FLAG_UPDATE indicates this. When this
> flag is set, ksmbd removes the share config from the shares hash table
> meaning that ksmbd_share_config_get() ends up requesting a share config
> from user space.
>
> Signed-off-by: Atte Heikkilä <atteh.mailbox@gmail.com>
Acked-by: Namjae Jeon <linkinjeon@kernel.org>
Thanks for your patch!
prev parent reply other threads:[~2022-08-09 0:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 22:02 [PATCH v2 1/3] ksmbd: request update to stale share config atheik
2022-08-08 22:02 ` [PATCH v2 2/3] ksmbd-tools: cleanup config group handling atheik
2022-08-08 22:02 ` [PATCH v2 3/3] ksmbd-tools: inform ksmbd of stale share config atheik
2022-08-10 8:06 ` Namjae Jeon
2022-08-09 0:38 ` Namjae Jeon [this message]
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=CAKYAXd9CBR92ydiBj+1u7hEnmahOK9V4qorJVzO0D1+iXJ4qzQ@mail.gmail.com \
--to=linkinjeon@kernel.org \
--cc=atteh.mailbox@gmail.com \
--cc=hyc.lee@gmail.com \
--cc=linux-cifs@vger.kernel.org \
--cc=smfrench@gmail.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.