From: Bixuan Cui <cuibixuan@huawei.com>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: <linux-kernel@vger.kernel.org>,
"Libin (Huawei)" <huawei.libin@huawei.com>,
"kangwen (A)" <kangwen1@huawei.com>,
"Leizhen (ThunderTown)" <thunder.leizhen@huawei.com>,
<ananth@linux.vnet.ibm.com>, <anil.s.keshavamurthy@intel.com>,
<davem@davemloft.net>
Subject: Re: [PATCH] kernel/kprobes: add check to avoid memory leaks
Date: Mon, 30 Oct 2017 19:34:39 +0800 [thread overview]
Message-ID: <59F70E4F.6070805@huawei.com> (raw)
In-Reply-To: <20171030134221.b2c17e36d4deb78a431a0067@kernel.org>
On 2017/10/30 12:42, Masami Hiramatsu wrote:
> I don't like this kind of check, since this is obviously caller's bug.
> Why doesn't each caller check this?
Thank you for your answer.
Thanks,
Bixuan Cui
prev parent reply other threads:[~2017-10-30 11:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 12:29 [PATCH] kernel/kprobes: add check to avoid memory leaks Bixuan Cui
2017-10-30 1:10 ` Bixuan Cui
2017-10-30 4:42 ` Masami Hiramatsu
2017-10-30 11:34 ` Bixuan Cui [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 \
--in-reply-to=59F70E4F.6070805@huawei.com \
--to=cuibixuan@huawei.com \
--cc=ananth@linux.vnet.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=davem@davemloft.net \
--cc=huawei.libin@huawei.com \
--cc=kangwen1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=thunder.leizhen@huawei.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