From: Petr Vorel <pvorel@suse.cz>
To: Avinesh Kumar <akumar@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2] getxattr04, 05: Change to docparse comment and typo fixes
Date: Wed, 6 Mar 2024 22:48:21 +0100 [thread overview]
Message-ID: <20240306214821.GA107948@pevik> (raw)
In-Reply-To: <20240305212410.18978-1-akumar@suse.de>
Hi Avinesh, Shiyang,
I merged with following improvements below. Thanks!
> +++ b/testcases/kernel/syscalls/getxattr/getxattr04.c
> @@ -4,13 +4,15 @@
> * Author: Xiao Yang <yangx.jy@cn.fujitsu.com>
> */
> -/*
> +/*\
> + * [Description]
> + *
> * This is a regression test for the race between getting an existing
> * xattr and setting/removing a large xattr. This bug leads to that
> * getxattr() fails to get an existing xattr and returns ENOATTR in xfs
> * filesystem.
> *
> - * Thie bug has been fixed in:
> + * This bug has been fixed in:
> *
> * commit 5a93790d4e2df73e30c965ec6e49be82fc3ccfce
> * Author: Brian Foster <bfoster@redhat.com>
Just single line:
* 5a93790d4e2d ("xfs: remove racy hasattr check from attr ops")
> diff --git a/testcases/kernel/syscalls/getxattr/getxattr05.c b/testcases/kernel/syscalls/getxattr/getxattr05.c
> index f12e2f813..069e2b3f9 100644
> --- a/testcases/kernel/syscalls/getxattr/getxattr05.c
> +++ b/testcases/kernel/syscalls/getxattr/getxattr05.c
> @@ -4,12 +4,14 @@
> * Author: Xiao Yang <yangx.jy@cn.fujitsu.com>
> */
> -/*
> - * Description:
> - * 1) Witout a user namespace, getxattr(2) should get same data when
> - * acquiring the value of system.posix_acl_access twice.
> - * 2) With/Without mapped root UID in a user namespaces, getxattr(2) should
> - * get same data when acquiring the value of system.posix_acl_access twice.
> +/*\
> + * [Description]
> + *
> + * This test verifies that:
Here still needs to be empty line, I haven't managed to send v2 of the change
[1] which would allow to format it without empty line.
> + * - Without a user namespace, getxattr(2) should get same data when
> + * acquiring the value of system.posix_acl_access twice.
> + * - With/Without mapped root UID in a user namespaces, getxattr(2) should
> + * get same data when acquiring the value of system.posix_acl_access twice.
> *
> * This issue included by getxattr05 has been fixed in kernel:
> * '82c9a927bc5d ("getxattr: use correct xattr length")'
no quotes:
* 82c9a927bc5d ("getxattr: use correct xattr length")
+ I dared to use a 12 chars hash in "linux-git" (originally 11).
Kind regards,
Petr
[1] https://patchwork.ozlabs.org/project/ltp/list/?series=388930&state=*
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2024-03-06 21:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-21 16:11 [LTP] [PATCH 1/2] getxattr04,05: Add [Description] tag Shiyang Ruan
2024-01-21 16:11 ` [LTP] [PATCH 2/2] getxattr01: Convert to new API Shiyang Ruan
2024-03-05 20:52 ` Avinesh Kumar
2024-03-14 10:13 ` [LTP] [PATCH v2] " Shiyang Ruan via ltp
2024-03-20 16:34 ` Petr Vorel
2024-03-20 16:37 ` Petr Vorel
2024-03-21 10:13 ` [LTP] [PATCH v3] " Shiyang Ruan via ltp
2024-03-22 5:33 ` Petr Vorel
2024-03-05 21:24 ` [LTP] [PATCH v2] getxattr04, 05: Change to docparse comment and typo fixes Avinesh Kumar
2024-03-06 21:48 ` Petr Vorel [this message]
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=20240306214821.GA107948@pevik \
--to=pvorel@suse.cz \
--cc=akumar@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.