From: Steven Rostedt <rostedt@goodmis.org>
To: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: Jens Remus <jremus@linux.ibm.com>,
x86@kernel.org, Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
linux-kernel@vger.kernel.org,
Indu Bhagat <indu.bhagat@oracle.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-perf-users@vger.kernel.org, Mark Brown <broonie@kernel.org>,
linux-toolchains@vger.kernel.org, Jordan Rome <jordalgo@meta.com>,
Sam James <sam@gentoo.org>,
linux-trace-kernel@vger.kernel.org,
Andrii Nakryiko <andrii.nakryiko@gmail.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Florian Weimer <fweimer@redhat.com>,
Andy Lutomirski <luto@kernel.org>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>
Subject: Re: [PATCH v3 09/19] unwind: Introduce sframe user space unwinding
Date: Wed, 13 Nov 2024 17:25:35 -0500 [thread overview]
Message-ID: <20241113172535.7af07f61@gandalf.local.home> (raw)
In-Reply-To: <20241113172118.6db57c42@gandalf.local.home>
On Wed, 13 Nov 2024 17:21:18 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:
> > diff --git a/fs/binfmt_elf.c b/fs/binfmt_elf.c
> > index 434c548f0837..64cc3c1188ca 100644
> > --- a/fs/binfmt_elf.c
> > +++ b/fs/binfmt_elf.c
> > @@ -842,7 +842,8 @@ static int load_elf_binary(struct linux_binprm *bprm)
> > int first_pt_load = 1;
> > unsigned long error;
> > struct elf_phdr *elf_ppnt, *elf_phdata, *interp_elf_phdata = NULL;
> > - struct elf_phdr *elf_property_phdata = NULL, *sframe_phdr = NULL;
> > + struct elf_phdr *elf_property_phdata = NULL;
> > + unsigned long sframe_vaddr = 0;
>
> Could not just save the pointer to the sframe phd, as it gets freed before we need it.
^^^
phdr
> > diff --git a/kernel/unwind/sframe.c b/kernel/unwind/sframe.c
> > index 933e47696e29..ca4ef0b72772 100644
> > --- a/kernel/unwind/sframe.c
> > +++ b/kernel/unwind/sframe.c
> > @@ -73,15 +73,15 @@ static int find_fde(struct sframe_section *sec, unsigned long ip,
> > struct sframe_fde *fde)
> > {
> > struct sframe_fde __user *first, *last, *found = NULL;
> > - u32 ip_off, func_off_low = 0, func_off_high = -1;
> > + s32 ip_off, func_off_low = INT_MIN, func_off_high = INT_MAX;
>
> The ip_off is a signed it. I wrote a program to dump out the sframe section
^^
int
> of files, and I had:
>
> ffffed88: (1020) size: 16 off: 146 num: 2 info: 1 rep:16
> ffffed98: (1030) size: 336 off: 154 num: 2 info:17 rep:16
> ffffefe1: (1279) size: 113 off: 0 num: 4 info: 0 rep: 0
> fffff052: (12ea) size: 54 off: 15 num: 3 info: 0 rep: 0
> fffff088: (1320) size: 167 off: 26 num: 3 info: 0 rep: 0
> fffff12f: (13c7) size: 167 off: 37 num: 4 info: 0 rep: 0
> fffff1d6: (146e) size: 167 off: 52 num: 4 info: 0 rep: 0
> fffff27d: (1515) size: 22 off: 67 num: 4 info: 0 rep: 0
> fffff293: (152b) size: 141 off: 82 num: 4 info: 0 rep: 0
> fffff320: (15b8) size: 81 off: 97 num: 4 info: 0 rep: 0
> fffff371: (1609) size: 671 off: 112 num: 4 info: 1 rep: 0
> fffff610: (18a8) size: 171 off: 131 num: 4 info: 0 rep: 0
>
> The above turns was created by a loop of:
^^^^^^^^^
items were
No idea why I typed that :-p
I can't blame jetlag anymore.
-- Steve
prev parent reply other threads:[~2024-11-13 22:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1730150953.git.jpoimboe@kernel.org>
[not found] ` <a94eb70a80c4a13dedb2655b7848304a992cb1b0.1730150953.git.jpoimboe@kernel.org>
[not found] ` <20241029135617.GB14555@noisy.programming.kicks-ass.net>
[not found] ` <20241029171752.4y67p3ob24riogpi@treble.attlocal.net>
[not found] ` <bcd11a07-45fb-442b-a25b-5cadc6aac0e6@efficios.com>
[not found] ` <20241029183440.fbwoistveyxneezt@treble.attlocal.net>
2024-10-30 13:44 ` [PATCH v3 11/19] unwind: Add deferred user space unwinding API Mathieu Desnoyers
2024-10-30 17:47 ` Josh Poimboeuf
2024-10-30 17:55 ` Josh Poimboeuf
2024-10-30 18:25 ` Josh Poimboeuf
[not found] ` <42c0a99236af65c09c8182e260af7bcf5aa1e158.1730150953.git.jpoimboe@kernel.org>
[not found] ` <20241105124053.523e93dd@gandalf.local.home>
2024-11-05 17:45 ` [PATCH v3 09/19] unwind: Introduce sframe user space unwinding Steven Rostedt
[not found] ` <1f83be89-b816-48a3-a7ee-9b72f07b558e@linux.ibm.com>
[not found] ` <20241113155040.6a9a1bed@gandalf.local.home>
[not found] ` <20241113211535.ghnw52wkgudkjvgv@jpoimboe>
[not found] ` <20241113171326.6d1ddc83@gandalf.local.home>
2024-11-13 22:21 ` Steven Rostedt
2024-11-13 22:25 ` Steven Rostedt [this message]
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=20241113172535.7af07f61@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=andrii.nakryiko@gmail.com \
--cc=broonie@kernel.org \
--cc=fweimer@redhat.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=indu.bhagat@oracle.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=jordalgo@meta.com \
--cc=jpoimboe@kernel.org \
--cc=jremus@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-toolchains@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=sam@gentoo.org \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox