From: Oleg Nesterov <oleg@redhat.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
mingo@kernel.org, alexander.shishkin@linux.intel.com,
eranian@google.com, linux-kernel@vger.kernel.org,
vince@deater.net, dvyukov@google.com, andi@firstfloor.org,
sasha.levin@oracle.com, Pratyush Anand <panand@redhat.com>
Subject: Re: [RFC][PATCH 4/7] perf: Fix scaling vs enable_on_exec
Date: Fri, 26 Feb 2016 03:25:12 +0100 [thread overview]
Message-ID: <20160226022512.GA29896@redhat.com> (raw)
In-Reply-To: <20160223214436.GC23528@krava.redhat.com>
On 02/23, Jiri Olsa wrote:
>
> so I finally got some reasonable backtrace and figured that crash finally:
>
> #7 [ffff8802751afcd0] general_protection at ffffffff817a69e8
> [exception RIP: special_mapping_fault+47]
> RIP: ffffffff811e40df RSP: ffff8802751afd88 RFLAGS: 00010282
> RAX: ffff8802747e8b68 RBX: 00007fffffffe080 RCX: c4712d0070657267
> RDX: ffff8802751afd98 RSI: ffff8802742c4f00 RDI: ffff8802747e8b68
> RBP: ffff8802751afd88 R8: 0000000000000000 R9: ffff8802751afe58
> R10: 00000000000001fe R11: 00003fffffe00000 R12: ffff8802742c4f00
> R13: ffff8802751afe58 R14: 0000000000000000 R15: ffff880273f59ff8
> ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0000
> #8 [ffff8802751afd90] __do_fault at ffffffff811db505
> #9 [ffff8802751afdf8] handle_mm_fault at ffffffff811e0b03
> #10 [ffff8802751afec8] __do_page_fault at ffffffff8106734a
> #11 [ffff8802751aff20] do_page_fault at ffffffff810675df
> #12 [ffff8802751aff50] page_fault at ffffffff817a6a48
>
>
> it was caused by:
> - f872f5400cc0 mm: Add a vm_special_mapping.fault() method
> that added call of vm_special_mapping::fault if it's defined
I guess it came from tip/x86...
> - and uprobes code not initializing this fault pointer properly,
> attached patch fixed the issue for me,
> Oleg, I'm not sure this is how you want to fix this though..
Thanks! I'll send a simple fix tomorrow.
Oleg.
next prev parent reply other threads:[~2016-02-26 2:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 14:37 [RFC][PATCH 0/7] perf: more fuzzer inspired patches Peter Zijlstra
2016-02-19 14:37 ` [RFC][PATCH 1/7] perf: Close install vs exit race Peter Zijlstra
2016-02-19 14:37 ` [RFC][PATCH 2/7] perf: Do not double free Peter Zijlstra
2016-02-19 14:37 ` [RFC][PATCH 3/7] perf: Allow perf_release() with !event->ctx Peter Zijlstra
2016-02-19 14:37 ` [RFC][PATCH 4/7] perf: Fix scaling vs enable_on_exec Peter Zijlstra
2016-02-23 15:27 ` Peter Zijlstra
2016-02-23 15:48 ` Jiri Olsa
2016-02-23 16:35 ` Pratyush Anand
2016-02-23 17:47 ` Peter Zijlstra
2016-02-24 11:53 ` Peter Zijlstra
2016-02-24 14:02 ` Peter Zijlstra
2016-02-24 16:02 ` Peter Zijlstra
2016-02-25 4:07 ` Pratyush Anand
2016-02-23 21:44 ` Jiri Olsa
2016-02-26 2:25 ` Oleg Nesterov [this message]
2016-02-19 14:37 ` [RFC][PATCH 5/7] perf: Fix cloning Peter Zijlstra
2016-02-19 14:37 ` [RFC][PATCH 6/7] perf: Fix race between event install and jump_labels Peter Zijlstra
2016-02-19 14:37 ` [RFC][PATCH 7/7] perf: Cure event->pending_disable race Peter Zijlstra
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=20160226022512.GA29896@redhat.com \
--to=oleg@redhat.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=dvyukov@google.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=panand@redhat.com \
--cc=peterz@infradead.org \
--cc=sasha.levin@oracle.com \
--cc=vince@deater.net \
/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.