From: Casey Schaufler <casey@schaufler-ca.com>
To: Roberto Sassu <roberto.sassu@huaweicloud.com>,
paul@paul-moore.com, jmorris@namei.org, serge@hallyn.com
Cc: linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, zohar@linux.ibm.com,
linux-unionfs@vger.kernel.org, miklos@szeredi.hu,
yoonjaeh@amazon.com, kamatam@amazon.com, mengcc@amazon.com,
Roberto Sassu <roberto.sassu@huawei.com>,
Casey Schaufler <casey@schaufler-ca.com>
Subject: Re: [RFC][PATCH 2/2] smack: Record transmuting in smk_transmuted
Date: Thu, 11 May 2023 10:13:27 -0700 [thread overview]
Message-ID: <25462ba8-ca34-e4cf-cdd2-cdd417f323ff@schaufler-ca.com> (raw)
In-Reply-To: <20230508170234.3595105-2-roberto.sassu@huaweicloud.com>
On 5/8/2023 10:02 AM, Roberto Sassu wrote:
> From: Roberto Sassu <roberto.sassu@huawei.com>
>
> smack_dentry_create_files_as() determines whether transmuting should occur
> based on the label of the parent directory the new inode will be added to,
> and not the label of the directory where it is created.
>
> This helps for example to do transmuting on overlayfs, since the latter
> first creates the inode in the working directory, and then moves it to the
> correct destination.
>
> However, despite smack_dentry_create_files_as() provides the correct label,
> smack_inode_init_security() does not know from passed information whether
> or not transmuting occurred. Without this information,
> smack_inode_init_security() cannot set SMK_INODE_CHANGED in smk_flags,
> which will result in the SMACK64TRANSMUTE xattr not being set in
> smack_d_instantiate().
>
> Thus, add the smk_transmuted field to the task_smack structure, and set it
> in smack_dentry_create_files_as() to smk_task if transmuting occurred. If
> smk_task is equal to smk_transmuted in smack_inode_init_security(), act as
> if transmuting was successful but without taking the label from the parent
> directory (the inode label was already set correctly from the current
> credentials in smack_inode_alloc_security()).
>
> Signed-off-by: Roberto Sassu <roberto.sassu@huawei.com>
Added to smack next.
> ---
> security/smack/smack.h | 1 +
> security/smack/smack_lsm.c | 41 +++++++++++++++++++++++++++-----------
> 2 files changed, 30 insertions(+), 12 deletions(-)
>
> diff --git a/security/smack/smack.h b/security/smack/smack.h
> index e2239be7bd6..aa15ff56ed6 100644
> --- a/security/smack/smack.h
> +++ b/security/smack/smack.h
> @@ -120,6 +120,7 @@ struct inode_smack {
> struct task_smack {
> struct smack_known *smk_task; /* label for access control */
> struct smack_known *smk_forked; /* label when forked */
> + struct smack_known *smk_transmuted;/* label when transmuted */
> struct list_head smk_rules; /* per task access rules */
> struct mutex smk_rules_lock; /* lock for the rules */
> struct list_head smk_relabel; /* transit allowed labels */
> diff --git a/security/smack/smack_lsm.c b/security/smack/smack_lsm.c
> index c7e37ed2799..6e270cf3fd3 100644
> --- a/security/smack/smack_lsm.c
> +++ b/security/smack/smack_lsm.c
> @@ -933,8 +933,9 @@ static int smack_inode_init_security(struct inode *inode, struct inode *dir,
> const struct qstr *qstr, const char **name,
> void **value, size_t *len)
> {
> + struct task_smack *tsp = smack_cred(current_cred());
> struct inode_smack *issp = smack_inode(inode);
> - struct smack_known *skp = smk_of_current();
> + struct smack_known *skp = smk_of_task(tsp);
> struct smack_known *isp = smk_of_inode(inode);
> struct smack_known *dsp = smk_of_inode(dir);
> int may;
> @@ -943,20 +944,34 @@ static int smack_inode_init_security(struct inode *inode, struct inode *dir,
> *name = XATTR_SMACK_SUFFIX;
>
> if (value && len) {
> - rcu_read_lock();
> - may = smk_access_entry(skp->smk_known, dsp->smk_known,
> - &skp->smk_rules);
> - rcu_read_unlock();
> + /*
> + * If equal, transmuting already occurred in
> + * smack_dentry_create_files_as(). No need to check again.
> + */
> + if (tsp->smk_task != tsp->smk_transmuted) {
> + rcu_read_lock();
> + may = smk_access_entry(skp->smk_known, dsp->smk_known,
> + &skp->smk_rules);
> + rcu_read_unlock();
> + }
>
> /*
> - * If the access rule allows transmutation and
> - * the directory requests transmutation then
> - * by all means transmute.
> + * In addition to having smk_task equal to smk_transmuted,
> + * if the access rule allows transmutation and the directory
> + * requests transmutation then by all means transmute.
> * Mark the inode as changed.
> */
> - if (may > 0 && ((may & MAY_TRANSMUTE) != 0) &&
> - smk_inode_transmutable(dir)) {
> - isp = dsp;
> + if ((tsp->smk_task == tsp->smk_transmuted) ||
> + (may > 0 && ((may & MAY_TRANSMUTE) != 0) &&
> + smk_inode_transmutable(dir))) {
> + /*
> + * The caller of smack_dentry_create_files_as()
> + * should have overridden the current cred, so the
> + * inode label was already set correctly in
> + * smack_inode_alloc_security().
> + */
> + if (tsp->smk_task != tsp->smk_transmuted)
> + isp = dsp;
> issp->smk_flags |= SMK_INODE_CHANGED;
> }
>
> @@ -4767,8 +4782,10 @@ static int smack_dentry_create_files_as(struct dentry *dentry, int mode,
> * providing access is transmuting use the containing
> * directory label instead of the process label.
> */
> - if (may > 0 && (may & MAY_TRANSMUTE))
> + if (may > 0 && (may & MAY_TRANSMUTE)) {
> ntsp->smk_task = isp->smk_inode;
> + ntsp->smk_transmuted = ntsp->smk_task;
> + }
> }
> return 0;
> }
next prev parent reply other threads:[~2023-05-11 17:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 17:02 [RFC][PATCH 1/2] smack: Retrieve transmuting information in smack_inode_getsecurity() Roberto Sassu
2023-05-08 17:02 ` [RFC][PATCH 2/2] smack: Record transmuting in smk_transmuted Roberto Sassu
2023-05-11 17:13 ` Casey Schaufler [this message]
2023-05-08 17:24 ` [RFC][PATCH 1/2] smack: Retrieve transmuting information in smack_inode_getsecurity() Casey Schaufler
2023-05-11 17:12 ` Casey Schaufler
2023-08-21 7:55 ` Munehisa Kamata
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=25462ba8-ca34-e4cf-cdd2-cdd417f323ff@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=jmorris@namei.org \
--cc=kamatam@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=mengcc@amazon.com \
--cc=miklos@szeredi.hu \
--cc=paul@paul-moore.com \
--cc=roberto.sassu@huawei.com \
--cc=roberto.sassu@huaweicloud.com \
--cc=serge@hallyn.com \
--cc=yoonjaeh@amazon.com \
--cc=zohar@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®