All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 0/2] ftrace: two fixes with func_probes handling
Date: Thu, 08 Aug 2019 20:45:04 +0530	[thread overview]
Message-ID: <1565277255.xyq4vg2zkj.naveen@linux.ibm.com> (raw)
In-Reply-To: <cover.1562249521.git.naveen.n.rao@linux.vnet.ibm.com>

Naveen N. Rao wrote:
> Two patches addressing bugs in ftrace function probe handling. The first 
> patch addresses a NULL pointer dereference reported by LTP tests, while 
> the second one is a trivial patch to address a missing check for return 
> value, found by code inspection.

Steven,
Can you please take a look at these patches?

Thanks,
Naveen


WARNING: multiple messages have this Message-ID (diff)
From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] ftrace: two fixes with func_probes handling
Date: Thu, 08 Aug 2019 20:45:04 +0530	[thread overview]
Message-ID: <1565277255.xyq4vg2zkj.naveen@linux.ibm.com> (raw)
In-Reply-To: <cover.1562249521.git.naveen.n.rao@linux.vnet.ibm.com>

Naveen N. Rao wrote:
> Two patches addressing bugs in ftrace function probe handling. The first 
> patch addresses a NULL pointer dereference reported by LTP tests, while 
> the second one is a trivial patch to address a missing check for return 
> value, found by code inspection.

Steven,
Can you please take a look at these patches?

Thanks,
Naveen


  parent reply	other threads:[~2019-08-08 15:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-04 14:34 [PATCH 0/2] ftrace: two fixes with func_probes handling Naveen N. Rao
2019-07-04 14:34 ` Naveen N. Rao
2019-07-04 14:34 ` [PATCH 1/2] ftrace: Fix NULL pointer dereference in t_probe_next() Naveen N. Rao
2019-07-04 14:34   ` Naveen N. Rao
2019-08-30 20:16   ` Steven Rostedt
2019-08-30 20:16     ` Steven Rostedt
2019-08-30 20:47   ` Steven Rostedt
2019-08-30 20:47     ` Steven Rostedt
2019-09-04  8:07     ` Naveen N. Rao
2019-09-04  8:07       ` Naveen N. Rao
2019-07-04 14:34 ` [PATCH 2/2] ftrace: Check for successful allocation of hash Naveen N. Rao
2019-07-04 14:34   ` Naveen N. Rao
2019-08-08 15:15 ` Naveen N. Rao [this message]
2019-08-08 15:15   ` [PATCH 0/2] ftrace: two fixes with func_probes handling Naveen N. Rao
2019-08-08 15:17   ` Steven Rostedt
2019-08-08 15:17     ` Steven Rostedt
2019-08-30 20:14   ` Steven Rostedt
2019-08-30 20:14     ` 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=1565277255.xyq4vg2zkj.naveen@linux.ibm.com \
    --to=naveen.n.rao@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.