public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v6 4/5] Add fchmodat2_01 test
Date: Fri, 2 Aug 2024 13:35:46 +0200	[thread overview]
Message-ID: <20240802113546.GA1627111@pevik> (raw)
In-Reply-To: <20240802-fchmodat2-v6-4-dcb0293979b3@suse.com>

> From: Andrea Cervesato <andrea.cervesato@suse.com>

> This test verifies that fchmodat2() syscall is properly working with
> AT_SYMLINK_NOFOLLOW on regular files. When AT_SYMLINK_NOFOLLOW is used
> on symbolic links instead, we check for EOPNOTSUPP, since the feature is
> not implemented for VFS.
nit: I would replace "not implemented for VFS" with:

creating symlink is *blocked* by VFS since kernel commit 5d1f903f75a8
(previously it was never supposed to be supported by filesystems, there was a
series of bugs that lead to it working by accident on some filesystems)

> +++ b/testcases/kernel/syscalls/fchmodat2/fchmodat2_01.c
> @@ -0,0 +1,117 @@
> +// SPDX-License-Identifier: GPL-2.0-or-later
> +/*
> + * Copyright (C) 2024 SUSE LLC Andrea Cervesato <andrea.cervesato@suse.com>
> + */
> +
> +/*\
> + * [Description]
> + *
> + * This test verifies that fchmodat2() syscall is properly working with
> + * regular files, symbolic links and directories. AT_SYMLINK_NOFOLLOW is a
> + * special feature that is not enabled in VFS for symbolic links since
nit: maybe s/ enabled/blocked/
> + * (introduced by 5d1f903f75a8), so we only verify that EOPNOTSUPP is correctly
> + * raised when used on those particular files.
> + */

Feel free to merge whole patchset :).

Kind regards,
Petr

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

  reply	other threads:[~2024-08-02 11:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-02 10:59 [LTP] [PATCH v6 0/5] Add fchmodat2 testing suite Andrea Cervesato
2024-08-02 10:59 ` [LTP] [PATCH v6 1/5] Add SAFE_SYMLINKAT macro Andrea Cervesato
2024-08-02 11:31   ` Petr Vorel
2024-08-02 12:20     ` Andrea Cervesato via ltp
2024-08-02 10:59 ` [LTP] [PATCH v6 2/5] Add fchmodat2 syscalls definitions Andrea Cervesato
2024-08-02 10:59 ` [LTP] [PATCH v6 3/5] Add fchmodat2 fallback definition Andrea Cervesato
2024-08-02 11:30   ` Petr Vorel
2024-08-02 11:34     ` Andrea Cervesato via ltp
2024-08-05 15:36       ` Petr Vorel
2024-08-02 10:59 ` [LTP] [PATCH v6 4/5] Add fchmodat2_01 test Andrea Cervesato
2024-08-02 11:35   ` Petr Vorel [this message]
2024-08-02 10:59 ` [LTP] [PATCH v6 5/5] Add fchmodat2_02 test Andrea Cervesato

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=20240802113546.GA1627111@pevik \
    --to=pvorel@suse.cz \
    --cc=andrea.cervesato@suse.de \
    --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