From: Daniel Bristot de Oliveira <bristot@kernel.org>
To: jianchunfu <jianchunfu@cmss.chinamobile.com>, rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] rtla/utils: Use calloc and check the potential memory allocation failure
Date: Fri, 8 Jul 2022 14:37:22 +0200 [thread overview]
Message-ID: <43855674-0f0f-bdf9-4f52-72bb4bf7e863@kernel.org> (raw)
In-Reply-To: <20220615073348.6891-1-jianchunfu@cmss.chinamobile.com>
On 6/15/22 09:33, jianchunfu wrote:
> Replace malloc with calloc and add memory allocating check
> of mon_cpus before used.
>
> Fixes: 7d0dc9576dc3 ("rtla/timerlat: Add --dma-latency option")
> Signed-off-by: jianchunfu <jianchunfu@cmss.chinamobile.com>
Acked-by: Daniel Bristot de Oliveira <bristot@kernel.org>
Thanks!
-- Daniel
next prev parent reply other threads:[~2022-07-08 12:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 7:33 [PATCH v2] rtla/utils: Use calloc and check the potential memory allocation failure jianchunfu
2022-07-08 12:37 ` Daniel Bristot de Oliveira [this message]
2022-07-12 1:17 ` Steven Rostedt
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=43855674-0f0f-bdf9-4f52-72bb4bf7e863@kernel.org \
--to=bristot@kernel.org \
--cc=jianchunfu@cmss.chinamobile.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.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).