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 v5 1/5] Add SAFE_SYMLINKAT macro
Date: Fri, 2 Aug 2024 11:47:32 +0200	[thread overview]
Message-ID: <20240802094732.GA1613449@pevik> (raw)
In-Reply-To: <20240802-fchmodat2-v5-1-bff2ec1a4f06@suse.com>

Hi Andrea,

> Signed-off-by: Andrea Cervesato <andrea.cervesato@suse.com>
> ---
>  include/safe_macros_fn.h  |  4 ++++
>  include/tst_safe_macros.h |  3 +++
>  lib/safe_macros.c         | 20 ++++++++++++++++++++
>  3 files changed, 27 insertions(+)

> diff --git a/include/safe_macros_fn.h b/include/safe_macros_fn.h
> index d256091b7..6d9e72e4f 100644
> --- a/include/safe_macros_fn.h
> +++ b/include/safe_macros_fn.h
> @@ -122,6 +122,10 @@ int safe_symlink(const char *file, const int lineno,
>                   void (cleanup_fn)(void), const char *oldpath,
>                   const char *newpath);

> +int safe_symlinkat(const char *file, const int lineno,
> +                 void (cleanup_fn)(void), const char *oldpath,
> +                 const int newdirfd, const char *newpath);
> +

IMHO we agreed that we don't touch legacy API unless really needed.
If I remember correctly (I'm sorry I don't have a link), Cyril was not against
modifying lib/safe_macros.c (I would be against there is no need to touch old
API at all), but he was against exposing safe_symlinkat() in old API headers.

@Cyril correct me please if I'm wrong.
@Andrea if not, would you mind to move things to include/tst_safe_macros.h
and lib/tst_safe_macros.c?

The code itself is correct.

Kind regards,
Petr

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

  reply	other threads:[~2024-08-02  9:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-02  8:23 [LTP] [PATCH v5 0/5] Add fchmodat2 testing suite Andrea Cervesato
2024-08-02  8:23 ` [LTP] [PATCH v5 1/5] Add SAFE_SYMLINKAT macro Andrea Cervesato
2024-08-02  9:47   ` Petr Vorel [this message]
2024-08-02  9:48     ` Cyril Hrubis
2024-08-02 10:02       ` Petr Vorel
2024-08-02 10:39       ` Andrea Cervesato via ltp
2024-08-02  8:23 ` [LTP] [PATCH v5 2/5] Add fchmodat2 syscalls definitions Andrea Cervesato
2024-08-02  9:49   ` Petr Vorel
2024-08-02  8:23 ` [LTP] [PATCH v5 3/5] Add fchmodat2 fallback definition Andrea Cervesato
2024-08-02  9:55   ` Petr Vorel
2024-08-02 10:38     ` Andrea Cervesato via ltp
2024-08-02 10:57       ` Petr Vorel
2024-08-02  8:23 ` [LTP] [PATCH v5 4/5] Add fchmodat2_01 test Andrea Cervesato
2024-08-02  8:47   ` Petr Vorel
2024-08-02  8:23 ` [LTP] [PATCH v5 5/5] Add fchmodat2_02 test Andrea Cervesato
2024-08-02 10:33   ` Petr Vorel
2024-08-02  9:58 ` [LTP] [PATCH v5 0/5] Add fchmodat2 testing suite Petr Vorel

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=20240802094732.GA1613449@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