Linux Test Project
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2 0/4] Add proper filesystem skiplist
Date: Thu, 11 Mar 2021 11:55:05 +0100	[thread overview]
Message-ID: <20210311105509.2701-1-chrubis@suse.cz> (raw)

This adds a proper .skip_filesystems array to the tst_test structure and
implements support for both test with .all_filesystems enabled and
disabled.

As a bonus point we get the list of filesystems that the test does not
support exported to the metadata as well.

Changes in v2:

* Add docs (as Jan requested)

* Move the skiplist detection from the is_supported_by_kernel()
  to tst_fs_is_supported()
  (as requested by Martin and Li)
  (which also fixed the double message reported by Peter)

* Fixed typos in tst_fs.h header (as requested by Peter)

Cyril Hrubis (4):
  lib: Add proper filesystem skiplist
  lib: tst_fs_type change fs names to lowercase
  lib: Apply the skip_filesystems to rest of test as well
  doc: Update docs on filesystem detection

 doc/test-writing-guidelines.txt               | 47 +++++++++++++------
 include/tst_fs.h                              | 23 ++++++---
 include/tst_test.h                            |  9 +++-
 lib/tst_fs_type.c                             | 36 +++++++-------
 lib/tst_supported_fs_types.c                  | 37 ++++++++++++---
 lib/tst_test.c                                | 14 +++++-
 testcases/kernel/syscalls/fcntl/fcntl33.c     | 19 +++-----
 .../kernel/syscalls/fsconfig/fsconfig01.c     |  2 +-
 testcases/kernel/syscalls/fsmount/fsmount01.c |  2 +-
 testcases/kernel/syscalls/fsmount/fsmount02.c |  2 +-
 testcases/kernel/syscalls/fsopen/fsopen01.c   |  2 +-
 testcases/kernel/syscalls/fspick/fspick01.c   |  2 +-
 testcases/kernel/syscalls/fspick/fspick02.c   |  2 +-
 .../kernel/syscalls/ioctl/ioctl_loop05.c      | 11 ++---
 .../kernel/syscalls/move_mount/move_mount01.c |  2 +-
 .../kernel/syscalls/move_mount/move_mount02.c |  2 +-
 .../kernel/syscalls/open_tree/open_tree01.c   |  2 +-
 .../kernel/syscalls/open_tree/open_tree02.c   |  2 +-
 .../sync_file_range/sync_file_range02.c       |  2 +-
 .../kernel/syscalls/vmsplice/vmsplice01.c     |  9 ++--
 .../kernel/syscalls/vmsplice/vmsplice02.c     |  9 ++--
 testcases/lib/tst_supported_fs.c              |  4 +-
 22 files changed, 152 insertions(+), 88 deletions(-)

-- 
2.26.2


             reply	other threads:[~2021-03-11 10:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11 10:55 Cyril Hrubis [this message]
2021-03-11 10:55 ` [LTP] [PATCH v2 1/4] lib: Add proper filesystem skiplist Cyril Hrubis
2021-03-12 11:06   ` [LTP] [PATCH v3] " Martin Doucha
2021-03-12 14:05     ` Cyril Hrubis
2021-03-12 17:00       ` Martin Doucha
2021-03-11 10:55 ` [LTP] [PATCH v2 2/4] lib: tst_fs_type change fs names to lowercase Cyril Hrubis
2021-03-11 10:55 ` [LTP] [PATCH v2 3/4] lib: Apply the skip_filesystems to rest of test as well Cyril Hrubis
2021-03-11 10:55 ` [LTP] [PATCH v2 4/4] doc: Update docs on filesystem detection Cyril Hrubis
2021-03-11 11:34   ` Petr Vorel
2021-03-11 12:46 ` [LTP] [PATCH v2 0/4] Add proper filesystem skiplist Li Wang

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=20210311105509.2701-1-chrubis@suse.cz \
    --to=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    /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