public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 7/7] Add ioctl_ficlone04 test
Date: Wed, 24 Jul 2024 22:06:57 +0200	[thread overview]
Message-ID: <ZqFe4Qxw78uMJZGC@rei> (raw)
In-Reply-To: <3c2626c4-5c26-4112-9c74-4cf9b4ecc3e0@suse.com>

Hi!
> I can't understand what's the best way to test all the combinations. As 
> you can see there are many flags, which means the amount of permutations 
> is big.
> Most of those flags are handled (indeed) in the wrong way, since most of 
> their permutations return EXDEV. The point is that the syscall has many 
> error codes, so it's complex to write a code that covers all possible 
> results.
> 
> My idea would be to have an array of errors to give to 
> TST_EXP_FAIL2_ARR() and to avoid any statement around fd_src/fd_dst, 
> because the amount of if/switch-case might explode with the number of 
> permutations.

The purpose of the tst_fd iterator is mainly to hammer syscalls with
different kinds of file descriptors and trigger code paths in the kernel
that are not excercies under normal circumstances. So it's fine to have
a single array with a few sensible errno codes and pass that in all the
cases.

-- 
Cyril Hrubis
chrubis@suse.cz

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2024-07-24 20:04 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-23  7:15 [LTP] [PATCH v2 0/7] Add ioctl_ficlone testing suite Andrea Cervesato
2024-07-23  7:15 ` [LTP] [PATCH v2 1/7] Add fallback definitions for lapi/fs.h Andrea Cervesato
2024-07-24 11:52   ` Cyril Hrubis
2024-07-24 16:29   ` Cyril Hrubis
2024-07-25  7:11     ` Li Wang
2024-07-25  9:18       ` Cyril Hrubis
2024-07-25 12:55       ` Petr Vorel
2024-07-25 15:17         ` Cyril Hrubis
2024-07-26 12:03           ` Li Wang
2024-07-23  7:15 ` [LTP] [PATCH v2 2/7] Add ioctl_ficlone01 test Andrea Cervesato
2024-07-23  7:15 ` [LTP] [PATCH v2 3/7] Add ioctl_ficlone02 test Andrea Cervesato
2024-07-29 11:53   ` Petr Vorel
2024-07-29 12:03     ` Cyril Hrubis
2024-07-29 21:29       ` Petr Vorel
2024-07-23  7:15 ` [LTP] [PATCH v2 4/7] Add ioctl_ficlone03 test Andrea Cervesato
2024-07-24 12:20   ` Cyril Hrubis
2024-07-23  7:15 ` [LTP] [PATCH v2 5/7] Add ioctl_ficlonerange01 test Andrea Cervesato
2024-07-24 15:24   ` Cyril Hrubis
2024-07-24 15:34     ` Cyril Hrubis
2024-07-23  7:15 ` [LTP] [PATCH v2 6/7] Add ioctl_ficlonerange02 test Andrea Cervesato
2024-07-24 15:37   ` Cyril Hrubis
2024-07-23  7:15 ` [LTP] [PATCH v2 7/7] Add ioctl_ficlone04 test Andrea Cervesato
2024-07-24 15:42   ` Cyril Hrubis
2024-07-24 19:36     ` Andrea Cervesato via ltp
2024-07-24 20:06       ` Cyril Hrubis [this message]
2024-07-25  7:16         ` Andrea Cervesato via ltp

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=ZqFe4Qxw78uMJZGC@rei \
    --to=chrubis@suse.cz \
    --cc=andrea.cervesato@suse.com \
    --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