From: Andrii Nakryiko <andrii@kernel.org>
To: bpf@vger.kernel.org
Cc: linux-mm@kvack.org, akpm@linux-foundation.org,
adobriyan@gmail.com, shakeel.butt@linux.dev, hannes@cmpxchg.org,
ak@linux.intel.com, osandov@osandov.com, song@kernel.org,
jannh@google.com, Andrii Nakryiko <andrii@kernel.org>
Subject: [PATCH v3 bpf-next 07/10] lib/buildid: don't limit .note.gnu.build-id to the first page in ELF
Date: Tue, 30 Jul 2024 13:39:11 -0700 [thread overview]
Message-ID: <20240730203914.1182569-8-andrii@kernel.org> (raw)
In-Reply-To: <20240730203914.1182569-1-andrii@kernel.org>
With freader we don't need to restrict ourselves to a single page, so
let's allow ELF notes to be at any valid position with the file.
We also merge parse_build_id() and parse_build_id_buf() as now the only
difference between them is note offset overflow, which makes sense to
check in all situations.
Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
---
lib/buildid.c | 26 ++++++--------------------
1 file changed, 6 insertions(+), 20 deletions(-)
diff --git a/lib/buildid.c b/lib/buildid.c
index 6b5558cd95bf..78cfb3048385 100644
--- a/lib/buildid.c
+++ b/lib/buildid.c
@@ -155,9 +155,8 @@ static void freader_cleanup(struct freader *r)
* 32-bit and 64-bit system, because Elf32_Nhdr and Elf64_Nhdr are
* identical.
*/
-static int parse_build_id_buf(struct freader *r,
- unsigned char *build_id, __u32 *size,
- u64 note_offs, Elf32_Word note_size)
+static int parse_build_id(struct freader *r, unsigned char *build_id, __u32 *size,
+ u64 note_offs, Elf32_Word note_size)
{
const char note_name[] = "GNU";
const size_t note_name_sz = sizeof(note_name);
@@ -166,6 +165,10 @@ static int parse_build_id_buf(struct freader *r,
u32 name_sz, desc_sz;
const char *data;
+ /* check for overflow */
+ if (note_offs + note_size < note_offs)
+ return -EINVAL;
+
while (note_offs + sizeof(Elf32_Nhdr) < note_end) {
nhdr = freader_fetch(r, note_offs, sizeof(Elf32_Nhdr) + note_name_sz);
if (!nhdr)
@@ -199,23 +202,6 @@ static int parse_build_id_buf(struct freader *r,
return -EINVAL;
}
-static inline int parse_build_id(struct freader *r,
- unsigned char *build_id,
- __u32 *size,
- u64 note_start_off,
- Elf32_Word note_size)
-{
- /* check for overflow */
- if (note_start_off + note_size < note_start_off)
- return -EINVAL;
-
- /* only supports note that fits in the first page */
- if (note_start_off + note_size > PAGE_SIZE)
- return -EINVAL;
-
- return parse_build_id_buf(r, build_id, size, note_start_off, note_size);
-}
-
/* Parse build ID from 32-bit ELF */
static int get_build_id_32(struct freader *r, unsigned char *build_id, __u32 *size)
{
--
2.43.0
next prev parent reply other threads:[~2024-07-30 20:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 20:39 [PATCH v3 bpf-next 00/10] Harden and extend ELF build ID parsing logic Andrii Nakryiko
2024-07-30 20:39 ` [PATCH v3 bpf-next 01/10] lib/buildid: harden " Andrii Nakryiko
2024-07-31 4:04 ` Andi Kleen
2024-07-31 21:54 ` Andrii Nakryiko
2024-07-30 20:39 ` [PATCH v3 bpf-next 02/10] lib/buildid: add single page-based file reader abstraction Andrii Nakryiko
2024-07-30 20:39 ` [PATCH v3 bpf-next 03/10] lib/buildid: take into account e_phoff when fetching program headers Andrii Nakryiko
2024-07-30 20:39 ` [PATCH v3 bpf-next 04/10] lib/buildid: remove single-page limit for PHDR search Andrii Nakryiko
2024-07-30 20:39 ` [PATCH v3 bpf-next 05/10] lib/buildid: rename build_id_parse() into build_id_parse_nofault() Andrii Nakryiko
2024-07-30 20:39 ` [PATCH v3 bpf-next 06/10] lib/buildid: implement sleepable build_id_parse() API Andrii Nakryiko
2024-07-31 21:56 ` Andrii Nakryiko
2024-08-05 18:30 ` Shakeel Butt
2024-07-30 20:39 ` Andrii Nakryiko [this message]
2024-07-30 20:39 ` [PATCH v3 bpf-next 08/10] bpf: decouple stack_map_get_build_id_offset() from perf_callchain_entry Andrii Nakryiko
2024-07-30 20:39 ` [PATCH v3 bpf-next 09/10] bpf: wire up sleepable bpf_get_stack() and bpf_get_task_stack() helpers Andrii Nakryiko
2024-07-30 20:39 ` [PATCH v3 bpf-next 10/10] selftests/bpf: add build ID tests Andrii Nakryiko
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=20240730203914.1182569-8-andrii@kernel.org \
--to=andrii@kernel.org \
--cc=adobriyan@gmail.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=bpf@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=jannh@google.com \
--cc=linux-mm@kvack.org \
--cc=osandov@osandov.com \
--cc=shakeel.butt@linux.dev \
--cc=song@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;
as well as URLs for NNTP newsgroup(s).