From: Petr Mladek <pmladek@suse.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@redhat.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Thiago Macieira <thiago.macieira@intel.com>,
Jiri Kosina <jkosina@suse.com>,
linux-kernel@vger.kernel.org, Petr Mladek <pmladek@suse.com>
Subject: [PATCH 0/2] clone/kprobe: Do not use do_fork() when not defined
Date: Wed, 23 Sep 2015 13:59:27 +0200 [thread overview]
Message-ID: <1443009569-1508-1-git-send-email-pmladek@suse.com> (raw)
The commit 3033f14ab78c32687 ("clone: support passing tls argument via C
rather than pt_regs magic") introduced _do_fork() that allowed to pass
@tls parameter.
The old do_fork() is defined only for architectures that are not ready
to use this way and do not define HAVE_COPY_THREAD_TLS.
1st patch fixes do_fork() declaration.
2nd patch fixes kprobe samples to work again.
BTW: I think about renaming _do_fork() to do_fork_tls(). Then it will
use the same naming scheme as copy_thread()/copy_thread_tls().
Petr Mladek (2):
clone: Declare do_fork() only when available
kprobe: Use _do_fork() in samples to make them work again
include/linux/sched.h | 2 ++
samples/kprobes/jprobe_example.c | 14 +++++++-------
samples/kprobes/kprobe_example.c | 6 +++---
samples/kprobes/kretprobe_example.c | 4 ++--
4 files changed, 14 insertions(+), 12 deletions(-)
--
1.8.5.6
next reply other threads:[~2015-09-23 11:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 11:59 Petr Mladek [this message]
2015-09-23 11:59 ` [PATCH 1/2] clone: Declare do_fork() only when available Petr Mladek
2015-09-23 20:43 ` Andrew Morton
2015-09-23 11:59 ` [PATCH 2/2] kprobe: Use _do_fork() in samples to make them work again Petr Mladek
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=1443009569-1508-1-git-send-email-pmladek@suse.com \
--to=pmladek@suse.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=jkosina@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=thiago.macieira@intel.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
all inboxes | Powered by JetHome®