All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petri Latvala <petri.latvala@intel.com>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: igt-dev@lists.freedesktop.org, chris@chris-wilson.co.uk
Subject: Re: [igt-dev] [PATCH v5 8/8] tests/fbdev: Add tests for read/writing with NULL-pointer buffers
Date: Thu, 19 Nov 2020 16:11:49 +0200	[thread overview]
Message-ID: <20201119141149.GK7444@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20201119134746.28020-9-tzimmermann@suse.de>

On Thu, Nov 19, 2020 at 02:47:46PM +0100, Thomas Zimmermann wrote:
> Trying to read and write with a NULL-pointer buffer should fail and
> report EFAULT.
> 
> v4:
> 	* replace igt_require() by igt_assert() in "nullptr" (Petri)

But they're still igt_requires in there?


-- 
Petri Latvala


> 	* add nullptr test to CI
> v3:
> 	* put igt_describe() before igt_subtest() (Petri)
> 
> Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
> ---
>  tests/fbdev.c                         | 11 +++++++++++
>  tests/intel-ci/fast-feedback.testlist |  1 +
>  2 files changed, 12 insertions(+)
> 
> diff --git a/tests/fbdev.c b/tests/fbdev.c
> index 62aa99b4..c6139124 100644
> --- a/tests/fbdev.c
> +++ b/tests/fbdev.c
> @@ -229,6 +229,17 @@ static void framebuffer_tests(int fd)
>  		igt_assert_f(ret == 0, "read at EOF, ret=%zd\n", ret);
>  	}
>  
> +	igt_describe("Check framebuffer access with NULL");
> +	igt_subtest("nullptr") {
> +		ssize_t ret;
> +
> +		ret = pread(fd, NULL, fix_info.smem_len, 0);
> +		igt_require_f((ret == -1) && (errno == EFAULT), "reading into NULL did not return EFAULT, ret=%zd\n", ret);
> +
> +		ret = pwrite(fd, NULL, fix_info.smem_len, 0);
> +		igt_require_f((ret == -1) && (errno == EFAULT), "writing from NULL did not return EFAULT, ret=%zd\n", ret);
> +	}
> +
>  	igt_fixture {
>  		free(buf);
>  		memset(map, 0, fix_info.smem_len); // don't leave garbage on the screen
> diff --git a/tests/intel-ci/fast-feedback.testlist b/tests/intel-ci/fast-feedback.testlist
> index 0423de80..71bbd173 100644
> --- a/tests/intel-ci/fast-feedback.testlist
> +++ b/tests/intel-ci/fast-feedback.testlist
> @@ -4,6 +4,7 @@ igt@core_auth@basic-auth
>  igt@debugfs_test@read_all_entries
>  igt@fbdev@eof
>  igt@fbdev@info
> +igt@fbdev@nullptr
>  igt@fbdev@read
>  igt@fbdev@unaligned-read
>  igt@fbdev@unaligned-write
> -- 
> 2.29.2
> 
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2020-11-19 14:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-19 13:47 [igt-dev] [PATCH v5 0/8] Test cases for fbdev Thomas Zimmermann
2020-11-19 13:47 ` [igt-dev] [PATCH v5 1/8] tests/fbdev: Move existing tests into separate subgroups Thomas Zimmermann
2020-11-19 13:47 ` [igt-dev] [PATCH v5 2/8] tests/fbdev: Map framebuffer in igt_fixture Thomas Zimmermann
2020-11-19 13:47 ` [igt-dev] [PATCH v5 3/8] tests/fbdev: Add tests for read operations on framebuffer Thomas Zimmermann
2020-11-19 13:47 ` [igt-dev] [PATCH v5 4/8] tests/fbdev: Add tests for unaligned reads on framebuffer memory Thomas Zimmermann
2020-11-19 14:13   ` Petri Latvala
2020-11-19 13:47 ` [igt-dev] [PATCH v5 5/8] tests/fbdev: Add tests for write operations on framebuffer Thomas Zimmermann
2020-11-19 13:47 ` [igt-dev] [PATCH v5 6/8] tests/fbdev: Add tests for unaligned writes on framebuffer memory Thomas Zimmermann
2020-11-19 13:47 ` [igt-dev] [PATCH v5 7/8] tests/fbdev: Add tests for accessing framebuffer near EOF Thomas Zimmermann
2020-11-19 13:47 ` [igt-dev] [PATCH v5 8/8] tests/fbdev: Add tests for read/writing with NULL-pointer buffers Thomas Zimmermann
2020-11-19 14:11   ` Petri Latvala [this message]
2020-11-20  8:23     ` Thomas Zimmermann
2020-11-19 16:52 ` [igt-dev] ✗ Fi.CI.BAT: failure for Test cases for fbdev 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=20201119141149.GK7444@platvala-desk.ger.corp.intel.com \
    --to=petri.latvala@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=tzimmermann@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.