All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <bauerman@linux.ibm.com>
To: linux-kselftest@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Shuah Khan <shuah@kernel.org>,
	Andrea Arcangeli <aarcange@redhat.com>,
	Mike Rapoport <rppt@linux.vnet.ibm.com>,
	Prakash Sangappa <prakash.sangappa@oracle.com>,
	Thiago Jung Bauermann <bauerman@linux.ibm.com>
Subject: [PATCH v3 0/4] userfaultfd: selftest: Improve behavior with older kernels
Date: Tue, 28 Aug 2018 14:26:04 -0300	[thread overview]
Message-ID: <20180828172608.30075-1-bauerman@linux.ibm.com> (raw)

Hello,

This version of the series is unchanged from v2 except for the last patch
which is completely new, and is provided by Mike Rapoport.

Original series description:

> A tester ran the upstream selftest on a distro kernel and sounded the
> alarm when it reported failures for features which aren't included in
> that kernel.
> 
> This patch set improves the test behavior in that scenario.

Changes since v2:

- Added Mike Rapoport's Reviewed-by's and Acked-by's to patches 1-3. 
- Replaced patch 4/4 by the one provided by Mike Rapoport.

Changes since v1:

- Patch "userfaultfd: selftest: Skip test if userfaultfd() syscall
  not supported"
  - New patch, suggested by Mike Rapoport.

- Patch "userfaultfd: selftest: Skip test if a feature isn't supported"
  - Try running other tests even if one (or more) of them returns KSFT_SKIP.

- Patch "userfaultfd: selftest: Cope if shmem doesn't support zeropage"
  - Ignore lack of UFFDIO_ZEROPAGE in userfaultfd_events_test() and
    userfaultfd_stress().
  - Make userfaultfd_zeropage_test() return KSFT_SKIP if UFFDIO_ZEROPAGE
    isn't supported.

Mike Rapoport (1):
  userfaultfd: selftest: make supported range ioctl verification more
    robust

Thiago Jung Bauermann (3):
  userfaultfd: selftest: Fix checking of userfaultfd_open() result
  userfaultfd: selftest: Skip test if userfaultfd() syscall not
    supported
  userfaultfd: selftest: Skip test if a feature isn't supported

 tools/testing/selftests/vm/userfaultfd.c | 113 +++++++++++++++++++------------
 1 file changed, 69 insertions(+), 44 deletions(-)


WARNING: multiple messages have this Message-ID (diff)
From: bauerman at linux.ibm.com (Thiago Jung Bauermann)
Subject: [PATCH v3 0/4] userfaultfd: selftest: Improve behavior with older kernels
Date: Tue, 28 Aug 2018 14:26:04 -0300	[thread overview]
Message-ID: <20180828172608.30075-1-bauerman@linux.ibm.com> (raw)

Hello,

This version of the series is unchanged from v2 except for the last patch
which is completely new, and is provided by Mike Rapoport.

Original series description:

> A tester ran the upstream selftest on a distro kernel and sounded the
> alarm when it reported failures for features which aren't included in
> that kernel.
> 
> This patch set improves the test behavior in that scenario.

Changes since v2:

- Added Mike Rapoport's Reviewed-by's and Acked-by's to patches 1-3. 
- Replaced patch 4/4 by the one provided by Mike Rapoport.

Changes since v1:

- Patch "userfaultfd: selftest: Skip test if userfaultfd() syscall
  not supported"
  - New patch, suggested by Mike Rapoport.

- Patch "userfaultfd: selftest: Skip test if a feature isn't supported"
  - Try running other tests even if one (or more) of them returns KSFT_SKIP.

- Patch "userfaultfd: selftest: Cope if shmem doesn't support zeropage"
  - Ignore lack of UFFDIO_ZEROPAGE in userfaultfd_events_test() and
    userfaultfd_stress().
  - Make userfaultfd_zeropage_test() return KSFT_SKIP if UFFDIO_ZEROPAGE
    isn't supported.

Mike Rapoport (1):
  userfaultfd: selftest: make supported range ioctl verification more
    robust

Thiago Jung Bauermann (3):
  userfaultfd: selftest: Fix checking of userfaultfd_open() result
  userfaultfd: selftest: Skip test if userfaultfd() syscall not
    supported
  userfaultfd: selftest: Skip test if a feature isn't supported

 tools/testing/selftests/vm/userfaultfd.c | 113 +++++++++++++++++++------------
 1 file changed, 69 insertions(+), 44 deletions(-)

WARNING: multiple messages have this Message-ID (diff)
From: bauerman@linux.ibm.com (Thiago Jung Bauermann)
Subject: [PATCH v3 0/4] userfaultfd: selftest: Improve behavior with older kernels
Date: Tue, 28 Aug 2018 14:26:04 -0300	[thread overview]
Message-ID: <20180828172608.30075-1-bauerman@linux.ibm.com> (raw)
Message-ID: <20180828172604.7rNB1N4Wa2yoSAVgj4Fdi90SLDB51AMvgQ6G6p6gvgY@z> (raw)

Hello,

This version of the series is unchanged from v2 except for the last patch
which is completely new, and is provided by Mike Rapoport.

Original series description:

> A tester ran the upstream selftest on a distro kernel and sounded the
> alarm when it reported failures for features which aren't included in
> that kernel.
> 
> This patch set improves the test behavior in that scenario.

Changes since v2:

- Added Mike Rapoport's Reviewed-by's and Acked-by's to patches 1-3. 
- Replaced patch 4/4 by the one provided by Mike Rapoport.

Changes since v1:

- Patch "userfaultfd: selftest: Skip test if userfaultfd() syscall
  not supported"
  - New patch, suggested by Mike Rapoport.

- Patch "userfaultfd: selftest: Skip test if a feature isn't supported"
  - Try running other tests even if one (or more) of them returns KSFT_SKIP.

- Patch "userfaultfd: selftest: Cope if shmem doesn't support zeropage"
  - Ignore lack of UFFDIO_ZEROPAGE in userfaultfd_events_test() and
    userfaultfd_stress().
  - Make userfaultfd_zeropage_test() return KSFT_SKIP if UFFDIO_ZEROPAGE
    isn't supported.

Mike Rapoport (1):
  userfaultfd: selftest: make supported range ioctl verification more
    robust

Thiago Jung Bauermann (3):
  userfaultfd: selftest: Fix checking of userfaultfd_open() result
  userfaultfd: selftest: Skip test if userfaultfd() syscall not
    supported
  userfaultfd: selftest: Skip test if a feature isn't supported

 tools/testing/selftests/vm/userfaultfd.c | 113 +++++++++++++++++++------------
 1 file changed, 69 insertions(+), 44 deletions(-)

             reply	other threads:[~2018-08-28 17:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-28 17:26 Thiago Jung Bauermann [this message]
2018-08-28 17:26 ` [PATCH v3 0/4] userfaultfd: selftest: Improve behavior with older kernels Thiago Jung Bauermann
2018-08-28 17:26 ` bauerman
2018-08-28 17:26 ` [PATCH v3 1/4] userfaultfd: selftest: Fix checking of userfaultfd_open() result Thiago Jung Bauermann
2018-08-28 17:26   ` Thiago Jung Bauermann
2018-08-28 17:26   ` bauerman
2018-08-28 17:26 ` [PATCH v3 2/4] userfaultfd: selftest: Skip test if userfaultfd() syscall not supported Thiago Jung Bauermann
2018-08-28 17:26   ` Thiago Jung Bauermann
2018-08-28 17:26   ` bauerman
2018-08-28 17:26 ` [PATCH v3 3/4] userfaultfd: selftest: Skip test if a feature isn't supported Thiago Jung Bauermann
2018-08-28 17:26   ` Thiago Jung Bauermann
2018-08-28 17:26   ` bauerman
2018-08-28 17:26 ` [PATCH v3 4/4] userfaultfd: selftest: make supported range ioctl verification more robust Thiago Jung Bauermann
2018-08-28 17:26   ` Thiago Jung Bauermann
2018-08-28 17:26   ` bauerman

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=20180828172608.30075-1-bauerman@linux.ibm.com \
    --to=bauerman@linux.ibm.com \
    --cc=aarcange@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=prakash.sangappa@oracle.com \
    --cc=rppt@linux.vnet.ibm.com \
    --cc=shuah@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 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.