] [RFC] tests/drm_read: Fix subtest
invalid-buffer
On Fri, May 28, 2021 at 10:02:47AM +0530, Vidya Srinivas wrote:
> Using (void *)-1 directly in read is aborting on chrome systems.
> Following message is seen.
>
> Starting subtest: invalid-buffer
> *** buffer overflow detected
On Fri, May 28, 2021 at 10:02:47AM +0530, Vidya Srinivas wrote:
> Using (void *)-1 directly in read is aborting on chrome systems.
> Following message is seen.
>
> Starting subtest: invalid-buffer
> *** buffer overflow detected ***: terminated
> Received signal SIGABRT.
> Stack trace:
> Aborted
Thank you very much Mark, for testing the patch and providing the "Tested-by"
tag.
Regards
Vidya
-Original Message-
From: Mark Yacoub
Sent: Saturday, June 5, 2021 12:13 AM
To: Srinivas, Vidya
Cc: intel-gfx@lists.freedesktop.org; igt-...@lists.freedesktop.org;
Almahallawy, Khaled ;
On Fri, May 28, 2021 at 12:41 AM Vidya Srinivas
wrote:
>
> Using (void *)-1 directly in read is aborting on chrome systems.
> Following message is seen.
>
> Starting subtest: invalid-buffer
> *** buffer overflow detected ***: terminated
> Received signal SIGABRT.
> Stack trace:
> Aborted (core
Using (void *)-1 directly in read is aborting on chrome systems.
Following message is seen.
Starting subtest: invalid-buffer
*** buffer overflow detected ***: terminated
Received signal SIGABRT.
Stack trace:
Aborted (core dumped)
Patch just adds a pointer variable and uses it in read.
