From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: linuxtestproject.agent@gmail.com
Cc: ltp@lists.linux.it
Subject: Re: [LTP] coredump01: New core_pattern specifiers test
Date: Fri, 04 Sep 2026 12:26:51 +0000 [thread overview]
Message-ID: <6a9ab90c.622c318d.bd035.fd0c@mx.google.com> (raw)
In-Reply-To: <20260904122012.9088-1-linuxtestproject.agent@gmail.com>
>
> This manually dispatches separate functions for the two test cases. Use a
> single struct tcase array and a generic .test callback, with
> .tcnt = ARRAY_SIZE(tcases), as required for multi-case tests.
no need for this.
>
> --- [PATCH 2/2] ---
>
> > } else if (ph[i].p_type == PT_LOAD) {
> > have_load = 1;
> > }
>
> This only proves that a PT_LOAD header exists, not that its data is present.
> A short dump_emit() after the headers and notes leaves WCOREDUMP set, so a
> truncated core can pass every check here. Validate p_offset + p_filesz against
> core_len with overflow-safe arithmetic for every file-backed segment.
>
this is valid
--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-09-04 12:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 11:03 [LTP] [PATCH v7 0/2] coredump testing suite Andrea Cervesato
2026-09-04 11:03 ` [LTP] [PATCH v7 1/2] coredump01: New core_pattern specifiers test Andrea Cervesato
2026-09-04 12:20 ` [LTP] " linuxtestproject.agent
2026-09-04 12:26 ` Andrea Cervesato via ltp [this message]
2026-09-08 6:27 ` Andrea Cervesato via ltp
2026-09-08 6:18 ` [LTP] [PATCH v7 1/2] " Li Wang
2026-09-04 11:03 ` [LTP] [PATCH v7 2/2] coredump02: Verify ELF structure and notes Andrea Cervesato
2026-09-08 6:20 ` Li Wang
-- strict thread matches above, loose matches on Subject: below --
2026-09-08 6:26 [LTP] [PATCH v8 1/2] coredump01: New core_pattern specifiers test Andrea Cervesato
2026-09-08 6:48 ` [LTP] " linuxtestproject.agent
2026-09-04 7:15 [LTP] [PATCH v6 1/2] " Andrea Cervesato
2026-09-04 7:52 ` [LTP] " linuxtestproject.agent
2026-09-03 7:21 [LTP] [PATCH v5] " Andrea Cervesato
2026-09-03 12:01 ` [LTP] " linuxtestproject.agent
2026-09-02 15:00 [LTP] [PATCH v4] " Andrea Cervesato
2026-09-02 17:44 ` [LTP] " linuxtestproject.agent
2026-09-03 7:22 ` Andrea Cervesato via ltp
2026-08-24 8:58 [LTP] [PATCH v3] " Andrea Cervesato
2026-08-24 9:49 ` [LTP] " linuxtestproject.agent
2026-08-20 18:47 [LTP] [PATCH] " Andrea Cervesato
2026-08-20 19:35 ` [LTP] " linuxtestproject.agent
2026-08-24 7:22 ` Andrea Cervesato via ltp
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=6a9ab90c.622c318d.bd035.fd0c@mx.google.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=linuxtestproject.agent@gmail.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