public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Ingo Molnar <mingo@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Al Viro <viro@ZenIV.linux.org.uk>
Subject: [PATCH 0/2] [GIT PULL] tracing: A couple of fixes with tracefs
Date: Sun, 25 Sep 2016 19:23:24 -0400	[thread overview]
Message-ID: <20160925232324.747135083@goodmis.org> (raw)


Linus,

Al Viro has been looking at the tracefs code, and has pointed out
some issues. This contains one fix by me and one by Al. I'm sure that
he'll come up with more but for now I tested these patches and they
don't appear to have any negative impact on tracing.

Please pull the latest trace-v4.8-rc7 tree, which can be found at:


  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
trace-v4.8-rc7

Tag SHA1: 7a41afe1fd2b8a81f979c6e00533b68b07af2519
Head SHA1: 1ae2293dd6d2f5c823cf97e60b70d03631cd622f


Al Viro (1):
      fix memory leaks in tracing_buffers_splice_read()

Steven Rostedt (Red Hat) (1):
      tracing: Move mutex to protect against resetting of seq data

----
 kernel/trace/trace.c | 29 ++++++++++++++++-------------
 1 file changed, 16 insertions(+), 13 deletions(-)

             reply	other threads:[~2016-09-25 23:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-25 23:23 Steven Rostedt [this message]
2016-09-25 23:23 ` [PATCH 1/2] tracing: Move mutex to protect against resetting of seq data Steven Rostedt
2016-09-25 23:23 ` [PATCH 2/2] fix memory leaks in tracing_buffers_splice_read() 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=20160925232324.747135083@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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