From: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>
To: Vignesh Raman <vignesh.raman@collabora.com>,
<igt-dev@lists.freedesktop.org>
Cc: helen.koike@collabora.com, daniels@collabora.com
Subject: Re: [igt-dev] [PATCH i-g-t] lib/igt_kms: Fix memory corruption
Date: Fri, 27 Oct 2023 15:25:52 +0530 [thread overview]
Message-ID: <2b05e124-6772-ec09-1b50-f1dbfa860d57@intel.com> (raw)
In-Reply-To: <7421357d-5adf-85b4-de1a-30eee373d86b@collabora.com>
Hi Vignesh,
On Thu-26-10-2023 03:15 pm, Vignesh Raman wrote:
> Hi Bhanu,
>
> On 26/10/23 10:18, Modem, Bhanuprakash wrote:
>
>> Why don't we use n_pipes = count_crtcs (before allocating the memory)?
>>
>> - display->n_pipes = IGT_MAX_PIPES;
>> + display->n_pipes = resources->count_crtcs;
>>
>
> If we dynamically allocate memory for display->pipes using count_crtcs
> instead of IGT_MAX_PIPES, subtest all-pipes is failing in the below tests,
> kms_cursor_legacy@forked-bo
> kms_cursor_legacy@forked-move
> kms_cursor_legacy@single-bo
> kms_cursor_legacy@single-move
> kms_cursor_legacy@torture-bo
> kms_cursor_legacy@torture-move
>
> Starting dynamic subtest: all-pipes
> Stack trace:
> #0 ../lib/igt_core.c:1988 __igt_fail_assert()
> #1 ../tests/kms_cursor_legacy.c:138 stress.constprop.0()
> #2 ../tests/kms_cursor_legacy.c:1942 __igt_unique____real_main1887()
> #3 ../tests/kms_cursor_legacy.c:1887 main()
> #4 [__libc_init_first+0x8a]
> #5 [__libc_start_main+0x85]
> #6 [_start+0x21]
> child 0 failed with exit status 98
> Dynamic subtest all-pipes: FAIL (0.021s)
> Subtest forked-bo: FAIL (43.029s)
> Test requirement not met in function igt_require_pipe_crc, file
> ../lib/igt_pipe_crc.c:211:
> Test requirement: fstatat(dir, "crtc-0/crc/control", &stat, 0) == 0
> CRCs not supported on this platform
> Last errno: 2, No such file or directory
> Test requirement not met in function igt_require_intel, file
> ../lib/drmtest.c:787:
> Test requirement: is_intel_device(fd)
> Last errno: 2, No such file or directory
> stderr:
> -------
> (kms_cursor_legacy:721) CRITICAL: Test assertion failure function
> stress, file ../tests/kms_cursor_legacy.c:158:
> (kms_cursor_legacy:721) CRITICAL: Failed assertion:
> igt_ioctl((display->drm_fd), ((((2U|1U) << (((0+8)+8)+14)) | ((('d')) <<
> (0+8)) | (((0xA3)) << 0) | ((((sizeof(struct drm_mode_cursor)))) <<
> ((0+8)+8)))), (&arg)) == 0
> (kms_cursor_legacy:721) CRITICAL: Last errno: 2, No such file or directory
> (kms_cursor_legacy:721) CRITICAL: error: -1 != 0
> (kms_cursor_legacy:722) CRITICAL: Test assertion failure function
> stress, file ../tests/kms_cursor_legacy.c:158:
> (kms_cursor_legacy:722) CRITICAL: Failed assertion:
> igt_ioctl((display->drm_fd), ((((2U|1U) << (((0+8)+8)+14)) | ((('d')) <<
> (0+8)) | (((0xA3)) << 0) | ((((sizeof(struct drm_mode_cursor)))) <<
> ((0+8)+8)))), (&arg)) == 0
> (kms_cursor_legacy:722) CRITICAL: Last errno: 2, No such file or directory
> (kms_cursor_legacy:722) CRITICAL: error: -1 != 0
> Dynamic subtest all-pipes failed.
>
> With the initial patch all-pipes subtest was passing.
Looks, these tests are considering crtc count as display->n_pipes (16),
but for_each_pipe() operates on IGT_MAX_PIPES (8) causing the failures.
>
>
>>> - for (i = 0; i < resources->count_crtcs; i++) {
>>> + for (i = 0; i < min(resources->count_crtcs, IGT_MAX_PIPES); i++) {
>>
>> With this change, we are missing the information of crtc index 7 to 15
>> in the display structure, aren't we?
>
> Yes agree. Do we need to fix the all-pipes subtest failure with your
> proposed solution?
IMHO, increasing IGT_MAX_PIPES to 16 would be the simplest solution.
@@ -68,8 +68,15 @@ enum pipe {
PIPE_D,
PIPE_E,
PIPE_F,
PIPE_G,
PIPE_H,
+ PIPE_I,
+ PIPE_J,
+ PIPE_K,
+ PIPE_L,
+ PIPE_M,
+ PIPE_N,
+ PIPE_O,
IGT_MAX_PIPES
};
- Bhanu
>
> Regards,
> Vignesh
next prev parent reply other threads:[~2023-10-27 9:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 2:20 [igt-dev] [PATCH i-g-t] lib/igt_kms: Fix memory corruption Vignesh Raman
2023-10-26 3:23 ` [igt-dev] ✓ CI.xeBAT: success for " Patchwork
2023-10-26 3:27 ` [igt-dev] ✓ Fi.CI.BAT: " Patchwork
2023-10-26 4:48 ` [igt-dev] [PATCH i-g-t] " Modem, Bhanuprakash
2023-10-26 9:45 ` Vignesh Raman
2023-10-27 9:55 ` Modem, Bhanuprakash [this message]
2023-10-27 11:58 ` Vignesh Raman
2023-10-27 7:38 ` [igt-dev] ✗ Fi.CI.IGT: failure for " Patchwork
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=2b05e124-6772-ec09-1b50-f1dbfa860d57@intel.com \
--to=bhanuprakash.modem@intel.com \
--cc=daniels@collabora.com \
--cc=helen.koike@collabora.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=vignesh.raman@collabora.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