All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sunil Mushran <sunil.mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 1/1] ocfs2: free memory allocated by security_inode_init_security
Date: Tue, 31 May 2011 10:13:34 -0700	[thread overview]
Message-ID: <4DE521BE.4080905@oracle.com> (raw)
In-Reply-To: <1306749283.3128.6.camel@localhost.localdomain>

On 05/30/2011 02:54 AM, Mimi Zohar wrote:
> On Mon, 2011-05-30 at 14:39 +0800, Tiger Yang wrote:
>> The LSM security_inode_init_security() hook allocates memory
>> for xattr name and value, expecting the caller to release
>> the memory afterwards.
>>
>> reported-by: Mimi Zohar<zohar@linux.vnet.ibm.com>
>> Signed-off-by: Tiger Yang<tiger.yang@oracle.com>
> Hi Tiger,
>
> Thanks for taking a look.  For the normal case, the memory is now freed,
> but not on failure.
>
> thanks,
>
> Mimi

Move the frees below leave. And just to be safe, specifically
init .name and .value to null while declaring.

>> ---
>>   fs/ocfs2/xattr.c |    2 ++
>>   1 files changed, 2 insertions(+), 0 deletions(-)
>>
>> diff --git a/fs/ocfs2/xattr.c b/fs/ocfs2/xattr.c
>> index 81ecf9c..e9b031e 100644
>> --- a/fs/ocfs2/xattr.c
>> +++ b/fs/ocfs2/xattr.c
>> @@ -7215,6 +7215,8 @@ int ocfs2_init_security_and_acl(struct inode *dir,
>>
>>   	ocfs2_inode_unlock(dir, 0);
>>   	brelse(dir_bh);
>> +	kfree(si.name);
>> +	kfree(si.value);
>>   leave:
>>   	return ret;
>>   }
>
>
> _______________________________________________
> Ocfs2-devel mailing list
> Ocfs2-devel at oss.oracle.com
> http://oss.oracle.com/mailman/listinfo/ocfs2-devel

      parent reply	other threads:[~2011-05-31 17:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-30  6:39 [Ocfs2-devel] [PATCH 1/1] ocfs2: free memory allocated by security_inode_init_security Tiger Yang
2011-05-30  9:54 ` Mimi Zohar
2011-05-31 16:44   ` Tiger Yang
2011-05-31 17:13   ` Sunil Mushran [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=4DE521BE.4080905@oracle.com \
    --to=sunil.mushran@oracle.com \
    --cc=ocfs2-devel@oss.oracle.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.