From: Casey Schaufler <casey@schaufler-ca.com>
To: Sergio Luis <sergio@larces.uece.br>
Cc: "Ahmed S. Darwish" <darwish.07@gmail.com>,
LSM <linux-security-module@vger.kernel.org>,
LKLM <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] smackfs: check for allocation failures in smk_set_access()
Date: Mon, 22 Dec 2008 21:03:03 -0800 [thread overview]
Message-ID: <49507107.4010809@schaufler-ca.com> (raw)
In-Reply-To: <494F148F.8070101@larces.uece.br>
Sergio Luis wrote:
> smackfs: check for allocation failures in smk_set_access()
>
> While adding a new subject/object pair to smack_list, smk_set_access()
> didn't check the return of kzalloc().
>
> This patch changes smk_set_access() to return 0 or -ENOMEM, based on
> kzalloc()'s return. It also updates its caller, smk_write_load(), to
> check for smk_set_access()'s return, given it is no longer a void
> return function.
>
> Signed-off-by: Sergio Luis <sergio@larces.uece.br>
> To: Casey Schaufler <casey@schaufler-ca.com>
> Cc: Ahmed S. Darwish <darwish.07@gmail.com>
> Cc: LSM <linux-security-module@vger.kernel.org>
> Cc: LKLM <linux-kernel@vger.kernel.org>
>
Acked-by: Casey Schaufler <casey@schaufler-ca.com>
> security/smack/smackfs.c | 20 ++++++++++++++++----
> 1 files changed, 16 insertions(+), 4 deletions(-)
>
> diff --git a/security/smack/smackfs.c b/security/smack/smackfs.c
> index c21d8c8..44eb933 100644
> --- a/security/smack/smackfs.c
> +++ b/security/smack/smackfs.c
> @@ -185,11 +185,15 @@ static int smk_open_load(struct inode *inode, struct file *file)
> * the subject/object pair and replaces the access that was
> * there. If the pair isn't found add it with the specified
> * access.
> + *
> + * Returns 0 if nothing goes wrong or -ENOMEM if it fails
> + * during the allocation of the new pair to add.
> */
> -static void smk_set_access(struct smack_rule *srp)
> +static int smk_set_access(struct smack_rule *srp)
> {
> struct smk_list_entry *sp;
> struct smk_list_entry *newp;
> + int ret = 0;
>
> mutex_lock(&smack_list_lock);
>
> @@ -202,14 +206,20 @@ static void smk_set_access(struct smack_rule *srp)
>
> if (sp == NULL) {
> newp = kzalloc(sizeof(struct smk_list_entry), GFP_KERNEL);
> + if (newp == NULL) {
> + ret = -ENOMEM;
> + goto out;
> + }
> +
> newp->smk_rule = *srp;
> newp->smk_next = smack_list;
> smack_list = newp;
> }
>
> +out:
> mutex_unlock(&smack_list_lock);
>
> - return;
> + return ret;
> }
>
> /**
> @@ -309,8 +319,10 @@ static ssize_t smk_write_load(struct file *file, const char __user *buf,
> goto out;
> }
>
> - smk_set_access(&rule);
> - rc = count;
> + rc = smk_set_access(&rule);
> +
> + if (!rc)
> + rc = count;
>
> out:
> kfree(data);
>
>
>
next prev parent reply other threads:[~2008-12-23 5:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 4:16 [PATCH] smackfs: check for allocation failures in smk_set_access() Sergio Luis
2008-12-23 5:03 ` Casey Schaufler [this message]
2008-12-25 1:17 ` James Morris
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=49507107.4010809@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=darwish.07@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sergio@larces.uece.br \
/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