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 v5 16/16] Add listmount04 test
Date: Tue, 8 Oct 2024 17:39:58 +0200	[thread overview]
Message-ID: <ZwVSTk7lHAffDpyo@yuki.lan> (raw)
In-Reply-To: <781538d9-fa64-4352-af94-6ee0edc7d2c4@suse.com>

Hi!
> >> +	{
> >> +		.req = &request_small,
> >> +		.mnt_ids = mnt_ids,
> >> +		.nr_mnt_ids = MNT_SIZE,
> >> +		.flags = 0,
> >> +		.exp_errno = EINVAL,
> >> +		.msg = "request has insufficient size",
> >> +	},
> > It took me a while to realize that this is a request with .size set to
> > 0, which is obviously rejected as invalid. Maybe it should be called
> > request_zero_size instead.
> This is actually a request with a small memory size for mnt_id_req. I 
> remove 4 bytes allocation from the struct, so it doesn't make sense 
> request_zero_size.

But you pass the size as a zero, at least I do not see that you ever set
request_small->size.

> > Also there is quite a bit more errors we can trigger, looking at
> > statmount kernel syscall we can easily trigger at least:
> >
> > - param > 0 && param <= MNT_UNIUQE_ID_OFFSET -> EINVAL
> > - spare != 0 -> EINVAL
> > - nonexisting mnt_ns_id -> ENOENT
> >
> Andrea

-- 
Cyril Hrubis
chrubis@suse.cz

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

      reply	other threads:[~2024-10-08 15:41 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-08  9:41 [LTP] [PATCH v5 00/16] statmount/listmount testing suites Andrea Cervesato
2024-10-08  9:41 ` [LTP] [PATCH v5 01/16] Add SAFE_STATX macro Andrea Cervesato
2024-10-08  9:41 ` [LTP] [PATCH v5 02/16] Add TST_EXP_EQ_STR macro Andrea Cervesato
2024-10-08  9:41 ` [LTP] [PATCH v5 03/16] Add listmount/statmount syscalls Andrea Cervesato
2024-10-08  9:41 ` [LTP] [PATCH v5 04/16] Add listmount/statmount fallback declarations Andrea Cervesato
2024-10-08  9:41 ` [LTP] [PATCH v5 05/16] Add listmount01 test Andrea Cervesato
2024-10-08  9:41 ` [LTP] [PATCH v5 06/16] Add listmount02 test Andrea Cervesato
2024-10-08  9:42 ` [LTP] [PATCH v5 07/16] Add statmount01 test Andrea Cervesato
2024-10-08 11:54   ` Cyril Hrubis
2024-10-08  9:42 ` [LTP] [PATCH v5 08/16] Add statmount02 test Andrea Cervesato
2024-10-08  9:42 ` [LTP] [PATCH v5 09/16] Add statmount03 test Andrea Cervesato
2024-10-08  9:42 ` [LTP] [PATCH v5 10/16] Add statmount04 test Andrea Cervesato
2024-10-08  9:42 ` [LTP] [PATCH v5 11/16] Add statmount05 test Andrea Cervesato
2024-10-08 12:03   ` Cyril Hrubis
2024-10-08 13:57     ` Andrea Cervesato via ltp
2024-10-08 14:11       ` Andrea Cervesato via ltp
2024-10-08  9:42 ` [LTP] [PATCH v5 12/16] Add statmount06 test Andrea Cervesato
2024-10-08  9:42 ` [LTP] [PATCH v5 13/16] Add statmount07 test Andrea Cervesato
2024-10-08 12:27   ` Cyril Hrubis
2024-10-08  9:42 ` [LTP] [PATCH v5 14/16] Add statmount08 test Andrea Cervesato
2024-10-08 12:05   ` Cyril Hrubis
2024-10-08  9:42 ` [LTP] [PATCH v5 15/16] Add listmount03 test Andrea Cervesato
2024-10-08 12:08   ` Cyril Hrubis
2024-10-08  9:42 ` [LTP] [PATCH v5 16/16] Add listmount04 test Andrea Cervesato
2024-10-08 15:00   ` Cyril Hrubis
2024-10-08 15:33     ` Andrea Cervesato via ltp
2024-10-08 15:39       ` Cyril Hrubis [this message]

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=ZwVSTk7lHAffDpyo@yuki.lan \
    --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