From: "Amit K. Arora" <aarora@linux.vnet.ibm.com>
To: Alex Tomas <alex@clusterfs.com>
Cc: Mingming Cao <cmm@us.ibm.com>,
linux-ext4@vger.kernel.org, suparna@in.ibm.com
Subject: Re: [PATCH 1/1 version2] Extent overlap bugfix in ext4
Date: Thu, 4 Jan 2007 16:46:16 +0530 [thread overview]
Message-ID: <20070104111616.GA15920@amitarora.in.ibm.com> (raw)
In-Reply-To: <m3d55vf5r4.fsf@bzzz.home.net>
On Thu, Jan 04, 2007 at 01:25:35PM +0300, Alex Tomas wrote:
> >>>>> Amit K Arora (AKA) writes:
>
> AKA> +int ext4_ext_check_overlap(struct inode *inode,
> AKA> + struct ext4_extent *newext,
> AKA> + unsigned long *block)
> AKA> +{
> AKA> + struct ext4_ext_path *path;
> AKA> + unsigned int depth, b1, len1;
> AKA> + int ret = 0;
> AKA> +
> AKA> + b1 = le32_to_cpu(newext->ee_block);
> AKA> + len1 = le16_to_cpu(newext->ee_len);
> AKA> + path = ext4_ext_find_extent(inode, b1, NULL);
> AKA> + if (IS_ERR(path)) {
> AKA> + ret = PTR_ERR(path);
> AKA> + goto out;
> AKA> + }
> AKA> + depth = ext_depth(inode);
> AKA> + BUG_ON(path[depth].p_ext == NULL && depth != 0);
> AKA> +
> AKA> + *block = ext4_ext_next_allocated_block(path);
> AKA> + if (*block == EXT_MAX_BLOCK)
> AKA> + goto out;
> AKA> +
> AKA> + if (b1 + len1 > *block)
> AKA> + ret = 1;
> AKA> +out:
> AKA> + return ret;
>
> <AT> ext4_ext_find_extent() allocates 'path', I'd expect
> <AT> kfree() in the function.
Ok. I will add following after "out:"
if (path) {
ext4_ext_drop_refs(path);
kfree(path);
}
And also set "path = NULL;" before calling "goto out", incase
ext4_ext_find_extent() returns an error.
--
Regards,
Amit Arora
next prev parent reply other threads:[~2007-01-04 11:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-02 9:09 [PATCH 1/1] Extent overlap bugfix in ext4 Amit K. Arora
2007-01-02 9:25 ` Alex Tomas
2007-01-02 9:47 ` Amit K. Arora
2007-01-03 9:44 ` Alex Tomas
2007-01-03 18:07 ` Mingming Cao
2007-01-04 8:13 ` Amit K. Arora
2007-01-04 10:04 ` Alex Tomas
2007-01-04 18:23 ` Mingming Cao
2007-01-03 1:35 ` Mingming Cao
2007-01-03 6:06 ` Amit K. Arora
2007-01-04 8:54 ` [PATCH 1/1 version2] " Amit K. Arora
2007-01-04 10:25 ` Alex Tomas
2007-01-04 11:16 ` Amit K. Arora [this message]
2007-01-04 10:39 ` Alex Tomas
2007-01-04 11:27 ` Amit K. Arora
2007-01-04 11:37 ` Alex Tomas
2007-01-04 17:23 ` Amit K. Arora
2007-01-04 18:50 ` Mingming Cao
2007-01-04 19:19 ` Alex Tomas
2007-01-05 12:13 ` Amit K. Arora
2007-01-09 5:51 ` [PATCH 1/1 version3] " Amit K. Arora
2007-01-04 19:03 ` [PATCH 1/1 version2] " Alex Tomas
2007-01-04 19:47 ` Mingming Cao
2007-01-05 6:18 ` Amit K. Arora
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=20070104111616.GA15920@amitarora.in.ibm.com \
--to=aarora@linux.vnet.ibm.com \
--cc=alex@clusterfs.com \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=suparna@in.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;
as well as URLs for NNTP newsgroup(s).