All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v1] Rewritten symlink01 test
Date: Fri, 26 Jul 2024 17:47:35 +0200	[thread overview]
Message-ID: <ZqPFF7BovWnpZu8T@yuki> (raw)
In-Reply-To: <20240119092909.22806-1-andrea.cervesato@suse.de>

Hi!
> This test has been split and rewritten. Now it verifies the following
> symlink() syscall features:
> 
> - symbolic link is created from a non-existing folder
> - symbolic link is created from existing folder
> - syscall raises EEXIST when symbolic link already exists
> - syscall raises ENAMETOOLONG when path name is PATH_MAX long (or above)

I had a quick look at the status of this and it seems that there are
still a few missing parts, namely:

$ git grep symlink01 runtest/

runtest/syscalls:chdir01A symlink01 -T chdir01
runtest/syscalls:chmod01A symlink01 -T chmod01
runtest/syscalls:link01 symlink01 -T link01
runtest/syscalls:readlink01A symlink01 -T readlink01
runtest/syscalls:rename01A symlink01 -T rename01
runtest/syscalls:rmdir03A symlink01 -T rmdir03
runtest/syscalls:symlink01 symlink01
runtest/syscalls:unlink01 symlink01 -T unlink01

And the only patch apart from symlink01 conversion on patchwork seems to
be rename15:

https://patchwork.ozlabs.org/project/ltp/patch/20240424092357.11207-1-andrea.cervesato@suse.de/

-- 
Cyril Hrubis
chrubis@suse.cz

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

  parent reply	other threads:[~2024-07-26 15:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-19  9:29 [LTP] [PATCH v1] Rewritten symlink01 test Andrea Cervesato
2024-05-21 18:43 ` Petr Vorel
2024-05-21 20:25   ` Andrea Cervesato via ltp
2024-07-26 15:47 ` Cyril Hrubis [this message]
2024-07-26 16:25   ` 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=ZqPFF7BovWnpZu8T@yuki \
    --to=chrubis@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 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.