From: Tariq Saeed <tariq.x.saeed@oracle.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
mfasheh@suse.com, jlbec@evilplan.org
Cc: linux-fsdevel@vger.kernel.org, linux-security-module@vger.kernel.org
Subject: Re: [PATCH] ocfs2: Fix panic on kfree(xattr->name)
Date: Wed, 19 Mar 2014 12:28:06 -0700 [thread overview]
Message-ID: <5329EFC6.6070803@oracle.com> (raw)
In-Reply-To: <201403192155.IBI05253.OJQLOFVFSHFMtO@I-love.SAKURA.ne.jp>
The patch works. What is the plan for submitting to mainline?
Thanks,
-Tariq
On 03/19/2014 05:55 AM, Tetsuo Handa wrote:
> Tariq Saeed wrote:
>> This commit did not take into account the callers of this function who
>> assume they need to kfree() the name. It causes panic in ocfs2 on create
>> file. I am puzzled how did this commit got into the tree without changing
>> the callsites to NOT call kfree anymore. Am I missing something?
>
> You are right. It is my mistake. I didn't realize that ocfs2 is calling kfree()
> on the name field. Would you please test below patch?
>
> Regards.
> ----------
>>From 3940749700148f58265407987f813b773515661a Mon Sep 17 00:00:00 2001
> From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
> Date: Wed, 19 Mar 2014 21:49:21 +0900
> Subject: [PATCH] ocfs2: Fix panic on kfree(xattr->name)
>
> Commit 9548906b 'xattr: Constify ->name member of "struct xattr".' missed that
> ocfs2 is calling kfree(xattr->name). As a result, kernel panic occurs upon
> calling kfree(xattr->name) because xattr->name refers static constant names.
> This patch removes kfree(xattr->name) from ocfs2_mknod() and ocfs2_symlink().
>
> Reported-by: Tariq Saeed <tariq.x.saeed@oracle.com>
> Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
> Cc: <stable@vger.kernel.org> [3.12+]
> ---
> fs/ocfs2/namei.c | 2 --
> 1 files changed, 0 insertions(+), 2 deletions(-)
>
> diff --git a/fs/ocfs2/namei.c b/fs/ocfs2/namei.c
> index 3683643..feed025 100644
> --- a/fs/ocfs2/namei.c
> +++ b/fs/ocfs2/namei.c
> @@ -450,7 +450,6 @@ leave:
>
> brelse(new_fe_bh);
> brelse(parent_fe_bh);
> - kfree(si.name);
> kfree(si.value);
>
> ocfs2_free_dir_lookup_result(&lookup);
> @@ -1855,7 +1854,6 @@ bail:
>
> brelse(new_fe_bh);
> brelse(parent_fe_bh);
> - kfree(si.name);
> kfree(si.value);
> ocfs2_free_dir_lookup_result(&lookup);
> if (inode_ac)
>
next prev parent reply other threads:[~2014-03-19 19:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5328D286.2010209@oracle.com>
2014-03-19 12:55 ` [PATCH] ocfs2: Fix panic on kfree(xattr->name) Tetsuo Handa
2014-03-19 19:28 ` Tariq Saeed [this message]
2014-03-19 22:02 ` [Ocfs2-devel] " Tetsuo Handa
2014-03-19 22:02 ` Tetsuo Handa
2014-03-27 22:13 ` Tariq Saeed
2014-03-28 13:48 ` Tetsuo Handa
2014-03-28 22:13 ` 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=5329EFC6.6070803@oracle.com \
--to=tariq.x.saeed@oracle.com \
--cc=jlbec@evilplan.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
/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.