From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v3] syscalls/chown: Rewrite chown/chown04.c with the new api
Date: Wed, 12 May 2021 10:26:16 +0200 [thread overview]
Message-ID: <YJuRKEfwChqpx70G@pevik> (raw)
In-Reply-To: <20210506074621.167505-1-xieziyao@huawei.com>
Hi Ziyao,
> testcases/kernel/syscalls/chown/chown04.c | 228 +++++++---------------
...
> +/*\
> + * [Description]
> *
> - * Test Description:
> - * Verify that,
> - * 1) chown(2) returns -1 and sets errno to EPERM if the effective user id
> - * of process does not match the owner of the file and the process
> - * is not super user.
> - * 2) chown(2) returns -1 and sets errno to EACCES if search permission is
> - * denied on a component of the path prefix.
> - * 3) chown(2) returns -1 and sets errno to EFAULT if pathname points
> - * outside user's accessible address space.
> - * 4) chown(2) returns -1 and sets errno to ENAMETOOLONG if the pathname
> - * component is too long.
> - * 5) chown(2) returns -1 and sets errno to ENOTDIR if the directory
> - * component in pathname is not a directory.
> - * 6) chown(2) returns -1 and sets errno to ENOENT if the specified file
> - * does not exists.
> + * Verify that,
> + * 1) chown(2) returns -1 and sets errno to EPERM if the effective user id
> + * of process does not match the owner of the file and the process is not
> + * super user
> + * 2) chown(2) returns -1 and sets errno to EACCES if search permission is
> + * denied on a component of the path prefix
> + * 3) chown(2) returns -1 and sets errno to EFAULT if pathname points outside
> + * user's accessible address space
> + * 4) chown(2) returns -1 and sets errno to ENAMETOOLONG if the pathname
> + * component is too long
> + * 5) chown(2) returns -1 and sets errno to ENOENT if the specified file does
> + * not exists
> + * 6) chown(2) returns -1 and sets errno to ENOTDIR if the directory component
> + * in pathname is not a directory
> + * 7) chown(2) returns -1 and sets errno to ELOOP if too many symbolic links
> + * were encountered in resolving pathname
> + * 8) chown(2) returns -1 and sets errno to EROFS if the named file resides on
> + * a read-only filesystem
> */
FYI this is needed for proper docparse formatting:
/*\
* [Description]
*
* Verify that:
*
* 1. chown(2) returns -1 and sets errno to EPERM if the effective user id
* of process does not match the owner of the file and the process is not
* super user
* 2. chown(2) returns -1 and sets errno to EACCES if search permission is
* denied on a component of the path prefix
* 3. chown(2) returns -1 and sets errno to EFAULT if pathname points outside
* user's accessible address space
* 4. chown(2) returns -1 and sets errno to ENAMETOOLONG if the pathname
* component is too long
* 5. chown(2) returns -1 and sets errno to ENOENT if the specified file does
* not exists
* 6. chown(2) returns -1 and sets errno to ENOTDIR if the directory component
* in pathname is not a directory
* 7. chown(2) returns -1 and sets errno to ELOOP if too many symbolic links
* were encountered in resolving pathname
* 8. chown(2) returns -1 and sets errno to EROFS if the named file resides on
* a read-only filesystem
*/
Kind regards,
Petr
next prev parent reply other threads:[~2021-05-12 8:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 7:46 [LTP] [PATCH v3] syscalls/chown: Rewrite chown/chown04.c with the new api Xie Ziyao
2021-05-12 8:26 ` Petr Vorel [this message]
2021-05-12 9:19 ` Xie Ziyao
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=YJuRKEfwChqpx70G@pevik \
--to=pvorel@suse.cz \
--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