From: "Goel, Sameer" <sgoel@codeaurora.org>
To: Wei Liu <wei.liu2@citrix.com>, Julien Grall <julien.grall@arm.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
George Dunlap <george.dunlap@eu.citrix.com>,
Tomasz Nowicki <tn@semihalf.com>,
Ian Jackson <Ian.Jackson@citrix.com>,
Punit Agrawal <punit.agrawal@arm.com>,
Jan Beulich <jbeulich@suse.com>,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
xen-devel@lists.xenproject.org, nd@arm.com,
Robin Murphy <robin.murphy@arm.com>,
Shanker Donthineni <shankerd@codeaurora.org>
Subject: Re: [RFC 3/6] Introduce _xrealloc
Date: Mon, 28 Aug 2017 15:39:48 -0600 [thread overview]
Message-ID: <85a94fd9-0fe7-8294-ea3f-a98c6d99fc2f@codeaurora.org> (raw)
In-Reply-To: <20170609094448.lu2c67bzjeb3vcjt@citrix.com>
On 6/9/2017 3:44 AM, Wei Liu wrote:
> On Thu, Jun 08, 2017 at 08:49:01PM +0100, Julien Grall wrote:
>> CC the REST maintainers
>>
>> On 08/06/2017 20:30, Sameer Goel wrote:
>>> Introduce a memory realloc function.
>>>
>>> Signed-off-by: Sameer Goel <sgoel@codeaurora.org>
>>> ---
>>> xen/common/xmalloc_tlsf.c | 13 +++++++++++++
>>> xen/include/xen/xmalloc.h | 1 +
>>> 2 files changed, 14 insertions(+)
>>>
>>> diff --git a/xen/common/xmalloc_tlsf.c b/xen/common/xmalloc_tlsf.c
>>> index b256dc5..52385a8 100644
>>> --- a/xen/common/xmalloc_tlsf.c
>>> +++ b/xen/common/xmalloc_tlsf.c
>>> @@ -612,6 +612,19 @@ void *_xzalloc(unsigned long size, unsigned long align)
>>> return p ? memset(p, 0, size) : p;
>>> }
>>>
>>> +void *_xrealloc(void *p, unsigned long new_size, unsigned long align)
>>> +{
>>> + void *new_p = _xmalloc(new_size, align);
>>> +
>>> + if(new_p && p)
>>
>> Coding style: if ( ... )
>>
>>> + {
>>> + memcpy(new_p, p, new_size);
>
> This is wrong. How can you know if the area pointed to by p is at least
> new_size bytes long?
>
Agreed, I revisited the code and will remove _xrealloc and use xfree and _xmalloc instead.
Thanks,
Sameer
--
Qualcomm Datacenter Technologies as an affiliate of Qualcomm Technologies, Inc. Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-08-28 21:39 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 19:30 [RFC 0/6] IORT support and introduce fwspec Sameer Goel
2017-06-08 19:30 ` [RFC 1/6] passthrough/arm: Modify SMMU driver to use generic device definition Sameer Goel
2017-06-12 12:34 ` Julien Grall
2017-06-08 19:30 ` [RFC 2/6] arm64: Add definitions for fwnode_handle Sameer Goel
2017-06-08 19:47 ` Julien Grall
2017-06-08 19:59 ` Julien Grall
2017-06-08 21:42 ` Goel, Sameer
2017-06-08 21:57 ` Stefano Stabellini
2017-06-12 12:40 ` Julien Grall
2017-08-28 21:42 ` Goel, Sameer
2017-06-12 12:51 ` Julien Grall
2017-08-28 21:41 ` Goel, Sameer
2017-06-08 19:30 ` [RFC 3/6] Introduce _xrealloc Sameer Goel
2017-06-08 19:49 ` Julien Grall
2017-06-09 9:44 ` Wei Liu
2017-08-28 21:39 ` Goel, Sameer [this message]
2017-10-12 13:33 ` Julien Grall
2017-10-12 14:45 ` Wei Liu
2017-06-08 21:51 ` Stefano Stabellini
2017-06-08 19:30 ` [RFC 4/6] xen/passthrough/arm: Introduce iommu_fwspec Sameer Goel
2017-06-08 20:02 ` Julien Grall
2017-06-08 19:30 ` [RFC 5/6] ACPI: arm: Support for IORT Sameer Goel
2017-07-14 15:36 ` Jan Beulich
2017-06-08 19:30 ` [RFC 6/6] acpi:arm64: Add support for parsing IORT table Sameer Goel
2017-06-08 22:22 ` Stefano Stabellini
2017-06-09 11:15 ` Robin Murphy
2017-06-12 13:36 ` Julien Grall
2017-06-12 13:44 ` Jan Beulich
2017-06-21 16:55 ` Robin Murphy
2017-08-28 21:48 ` Goel, Sameer
2017-06-12 13:24 ` Julien Grall
2017-08-28 22:21 ` Goel, Sameer
2017-09-12 11:25 ` Julien Grall
2017-09-21 0:37 ` Goel, Sameer
2017-09-21 10:54 ` Julien Grall
2017-07-14 15:41 ` Jan Beulich
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=85a94fd9-0fe7-8294-ea3f-a98c6d99fc2f@codeaurora.org \
--to=sgoel@codeaurora.org \
--cc=Andrew.Cooper3@citrix.com \
--cc=Ian.Jackson@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=julien.grall@arm.com \
--cc=nd@arm.com \
--cc=punit.agrawal@arm.com \
--cc=robin.murphy@arm.com \
--cc=shankerd@codeaurora.org \
--cc=sstabellini@kernel.org \
--cc=tn@semihalf.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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).