All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Yang Xu <xuyang2018.jy@fujitsu.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/4] readlinkat: Remove readlinkat fallback definition
Date: Mon, 16 Oct 2023 10:09:13 +0200	[thread overview]
Message-ID: <20231016080913.GB840411@pevik> (raw)
In-Reply-To: <1694770631-9547-1-git-send-email-xuyang2018.jy@fujitsu.com>

Hi Yang,

> Looking at man readlinkat, it was added into kernel 2.6.16 and since the
> oldest kernel we support is 3.10 (see doc/supported-kernel-libc-versions
> .txt) we can as well completely drop this fallback definition.

Again, as I mentioned in v2 renameat() patch [1], the real reason for this lapi
function was IMHO missing glibc wrapper.  The correct git commit message should
have been glibc wrapper was added in ...

Also, without kernel support the function would not work at all, therefore it is
irrelevant when readlinkat was added into kernel. That applies to all git commit
messages. Due me merged v2 renameat() first, this is not applicable (patch must
be modified, I'm sorry).

This particular patch would deserve to note that since these 2 commits the lapi
is not even used (both released in 20230929 - a proof it can be really deleted):

0959b893a ("syscalls/readlinkat01: Convert to new API")
bcafe2971 ("syscalls/readlinkat02: Convert to new API")

Kind regards,
Petr

[1] https://lore.kernel.org/ltp/20231016080349.GA844528@pevik/

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

  parent reply	other threads:[~2023-10-16  8:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-15  9:37 [LTP] [PATCH 1/4] readlinkat: Remove readlinkat fallback definition Yang Xu
2023-09-15  9:37 ` [LTP] [PATCH 2/4] fchownat: Remove fchownat " Yang Xu
2023-09-15  9:37 ` [LTP] [PATCH 3/4] mkdirat: Remove mkdirat " Yang Xu
2023-09-15  9:37 ` [LTP] [PATCH 4/4] mknodat: Remove mknodat " Yang Xu
2023-10-13 10:10 ` [LTP] [PATCH 1/4] readlinkat: Remove readlinkat " Yang Xu (Fujitsu)
2023-10-16  8:09 ` Petr Vorel [this message]
2023-10-17  6:21   ` Yang Xu (Fujitsu)

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=20231016080913.GB840411@pevik \
    --to=pvorel@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=xuyang2018.jy@fujitsu.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.