From: Ammar Faizi <[email protected]>
To: Jeff Xie <[email protected]>
Cc: Ingo Molnar <[email protected]>,
Masami Hiramatsu <[email protected]>,
Steven Rostedt <[email protected]>,
Tom Zanussi <[email protected]>,
Linux Kernel Mailing List <[email protected]>
Subject: Re: [PATCH] tracing: Fix possible crash in ftrace_free_ftrace_ops()
Date: Mon, 9 May 2022 14:34:28 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAEr6+EC+Kg4AJ=BFxrOSQV+KHj5WSm=1FtYCAPrn1gFnZUk-fg@mail.gmail.com>
On 5/9/22 8:33 AM, Jeff Xie wrote:
> I am so sorry to bother you, this may be an invalid patch, kfree can
> return directly from null. ;-)
Yeah, kfree(NULL) is a valid call. There's no potential crash here.
--
Ammar Faizi
prev parent reply other threads:[~2022-05-09 7:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-08 16:18 [PATCH] tracing: Fix possible crash in ftrace_free_ftrace_ops() Jeff Xie
2022-05-09 1:33 ` Jeff Xie
2022-05-09 7:34 ` Ammar Faizi [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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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