From: Masami Hiramatsu <mhiramat@kernel.org>
To: Andrea Righi <righi.andrea@gmail.com>
Cc: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>,
Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Yonghong Song <yhs@fb.com>, Andy Lutomirski <luto@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kprobes: x86_64: blacklist non-attachable interrupt functions
Date: Sat, 8 Dec 2018 12:42:10 +0900 [thread overview]
Message-ID: <20181208124210.7f46eb88544e2e3899713052@kernel.org> (raw)
In-Reply-To: <20181207170026.GA1379@Dell>
On Fri, 7 Dec 2018 18:00:26 +0100
Andrea Righi <righi.andrea@gmail.com> wrote:
> On Sat, Dec 08, 2018 at 01:01:20AM +0900, Masami Hiramatsu wrote:
> > Hi Andrea and Ingo,
> >
> > Here is the patch what I meant. I just ran it on qemu-x86, and seemed working.
> > After introducing this patch, I will start adding arch_populate_kprobe_blacklist()
> > to some arches.
> >
> > Thank you,
> >
> > [RFC] kprobes: x86/kprobes: Blacklist symbols in arch-defined prohibited area
> >
> > From: Masami Hiramatsu <mhiramat@kernel.org>
> >
> > Blacklist symbols in arch-defined probe-prohibited areas.
> > With this change, user can see all symbols which are prohibited
> > to probe in debugfs.
> >
> > All archtectures which have custom prohibit areas should define
> > its own arch_populate_kprobe_blacklist() function, but unless that,
> > all symbols marked __kprobes are blacklisted.
> >
> > Reported-by: Andrea Righi <righi.andrea@gmail.com>
> > Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
> > ---
>
> [snip]
>
> > +int kprobe_add_ksym_blacklist(unsigned long entry)
> > +{
> > + struct kprobe_blacklist_entry *ent;
> > + unsigned long offset = 0, size = 0;
> > +
> > + if (!kernel_text_address(entry) ||
> > + !kallsyms_lookup_size_offset(entry, &size, &offset))
> > + return -EINVAL;
> > +
> > + ent = kmalloc(sizeof(*ent), GFP_KERNEL);
> > + if (!ent)
> > + return -ENOMEM;
> > + ent->start_addr = entry - offset;
> > + ent->end_addr = entry - offset + size;
>
> Do we need to take offset into account? The code before wasn't using it.
Yes, if we hit an alias symbol (zero-size), we forcibly increment address
and retry it. In that case, offset will be 1.
>
> > + INIT_LIST_HEAD(&ent->list);
> > + list_add_tail(&ent->list, &kprobe_blacklist);
> > +
> > + return (int)size;
> > +}
> > +
> > +/* Add functions in arch defined probe-prohibited area */
> > +int __weak arch_populate_kprobe_blacklist(void)
> > +{
> > + unsigned long entry;
> > + int ret = 0;
> > +
> > + for (entry = (unsigned long)__kprobes_text_start;
> > + entry < (unsigned long)__kprobes_text_end;
> > + entry += ret) {
> > + ret = kprobe_add_ksym_blacklist(entry);
> > + if (ret < 0)
> > + return ret;
> > + if (ret == 0) /* In case of alias symbol */
> > + ret = 1;
Here, we incremented.
Thank you,
> > + }
> > + return 0;
> > +}
> > +
> > /*
> > * Lookup and populate the kprobe_blacklist.
> > *
> > @@ -2104,26 +2142,20 @@ NOKPROBE_SYMBOL(dump_kprobe);
> > static int __init populate_kprobe_blacklist(unsigned long *start,
> > unsigned long *end)
> > {
> > + unsigned long entry;
> > unsigned long *iter;
> > - struct kprobe_blacklist_entry *ent;
> > - unsigned long entry, offset = 0, size = 0;
> > + int ret;
> >
> > for (iter = start; iter < end; iter++) {
> > entry = arch_deref_entry_point((void *)*iter);
> > -
> > - if (!kernel_text_address(entry) ||
> > - !kallsyms_lookup_size_offset(entry, &size, &offset))
> > + ret = kprobe_add_ksym_blacklist(entry);
> > + if (ret == -EINVAL)
> > continue;
> > -
> > - ent = kmalloc(sizeof(*ent), GFP_KERNEL);
> > - if (!ent)
> > - return -ENOMEM;
> > - ent->start_addr = entry;
> > - ent->end_addr = entry + size;
> > - INIT_LIST_HEAD(&ent->list);
> > - list_add_tail(&ent->list, &kprobe_blacklist);
> > + if (ret < 0)
> > + return ret;
> > }
> > - return 0;
> > +
> > + return arch_populate_kprobe_blacklist();
> > }
> >
> > /* Module notifier call back, checking kprobes on the module */
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2018-12-08 3:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 9:56 [PATCH] kprobes: x86_64: blacklist non-attachable interrupt functions Andrea Righi
2018-12-06 16:39 ` [tip:perf/urgent] kprobes/x86: Blacklist " tip-bot for Andrea Righi
2018-12-07 14:47 ` [PATCH] kprobes: x86_64: blacklist " Masami Hiramatsu
2018-12-07 16:01 ` Masami Hiramatsu
2018-12-07 17:00 ` Andrea Righi
2018-12-08 3:42 ` Masami Hiramatsu [this message]
2018-12-08 7:07 ` Andrea Righi
2018-12-07 17:58 ` Andrea Righi
2018-12-08 3:48 ` Masami Hiramatsu
2018-12-08 7:09 ` Andrea Righi
2018-12-16 16:07 ` Masami Hiramatsu
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=20181208124210.7f46eb88544e2e3899713052@kernel.org \
--to=mhiramat@kernel.org \
--cc=anil.s.keshavamurthy@intel.com \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=righi.andrea@gmail.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yhs@fb.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;
as well as URLs for NNTP newsgroup(s).