From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: Cyril Hrubis <chrubis@suse.cz>,
Andrea Cervesato <andrea.cervesato@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v5 3/7] fs: add file_setattr/file_getattr fallback definitions
Date: Thu, 7 Aug 2025 08:39:29 +0200 [thread overview]
Message-ID: <f3866144-54bf-4bec-ad75-e32fda873ba7@suse.com> (raw)
In-Reply-To: <aJN2YH2KYFpz4X-o@yuki.lan>
On 8/6/25 5:36 PM, Cyril Hrubis wrote:
> I wonder if we need configure checks for these (i.e. if glibc is going
> to add these as syscall wrappers) but I guess we can add them later on
> when needed.
Better to do it now, they seem to be an important update in the kernel.
I will send it in the next version.
- Andrea
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-08-07 6:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 17:44 [LTP] [PATCH v5 0/7] file_setattr/file_getattr testing suite Andrea Cervesato
2025-08-05 17:44 ` [LTP] [PATCH v5 1/7] Update LTP to the latest syscalls Andrea Cervesato
2025-08-06 15:11 ` Cyril Hrubis
2025-08-05 17:44 ` [LTP] [PATCH v5 2/7] fs: add struct fsxattr fallback definitions Andrea Cervesato
2025-08-06 15:28 ` Cyril Hrubis
2025-08-05 17:44 ` [LTP] [PATCH v5 3/7] fs: add file_setattr/file_getattr " Andrea Cervesato
2025-08-06 15:36 ` Cyril Hrubis
2025-08-07 6:39 ` Andrea Cervesato via ltp [this message]
2025-08-05 17:44 ` [LTP] [PATCH v5 4/7] Add file_attr01 test Andrea Cervesato
2025-08-06 15:03 ` Cyril Hrubis
2025-08-05 17:44 ` [LTP] [PATCH v5 5/7] Add file_attr02 test Andrea Cervesato
2025-08-06 14:56 ` Cyril Hrubis
2025-08-05 17:44 ` [LTP] [PATCH v5 6/7] Add file_attr03 test Andrea Cervesato
2025-08-06 14:42 ` Cyril Hrubis
2025-08-05 17:44 ` [LTP] [PATCH v5 7/7] Add file_attr04 test Andrea Cervesato
2025-08-06 14:23 ` Cyril Hrubis
2025-08-06 14:30 ` Cyril Hrubis
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=f3866144-54bf-4bec-ad75-e32fda873ba7@suse.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=andrea.cervesato@suse.de \
--cc=chrubis@suse.cz \
/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.