From: Cyril Hrubis <chrubis@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 1/7] Add fallback definitions for lapi/fs.h
Date: Thu, 25 Jul 2024 11:18:04 +0200 [thread overview]
Message-ID: <ZqIYTPN2Je61ZvOz@yuki> (raw)
In-Reply-To: <CAEemH2eaTSuyD3GT5QGwq7wDUe0eX79+-XpfnzhQqN8ztJ2Vog@mail.gmail.com>
Hi!
> Theoretically, we can remove it because that problem is addressed in
> Glibc-2.37 by:
>
>
> https://github.com/kraj/glibc/commit/774058d72942249f71d74e7f2b639f77184160a6
>
> It is essentially a glibc bug we don't need to fix that in LTP.
>
> We ever discussed in
> https://lists.linux.it/pipermail/ltp/2023-March/033138.html
>
> However, if we want LTP could be built with all the middle glibc versions
> (2.22 < glibc < 2.36)
> this might be thinking over. Because we announce support the minimal
> glibc-version is 2.22.
That does sound like we will need the workaround for quite some time.
Or maybe give up on including linux/fs.h and stick to the libc headers.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-07-25 9:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 7:15 [LTP] [PATCH v2 0/7] Add ioctl_ficlone testing suite Andrea Cervesato
2024-07-23 7:15 ` [LTP] [PATCH v2 1/7] Add fallback definitions for lapi/fs.h Andrea Cervesato
2024-07-24 11:52 ` Cyril Hrubis
2024-07-24 16:29 ` Cyril Hrubis
2024-07-25 7:11 ` Li Wang
2024-07-25 9:18 ` Cyril Hrubis [this message]
2024-07-25 12:55 ` Petr Vorel
2024-07-25 15:17 ` Cyril Hrubis
2024-07-26 12:03 ` Li Wang
2024-07-23 7:15 ` [LTP] [PATCH v2 2/7] Add ioctl_ficlone01 test Andrea Cervesato
2024-07-23 7:15 ` [LTP] [PATCH v2 3/7] Add ioctl_ficlone02 test Andrea Cervesato
2024-07-29 11:53 ` Petr Vorel
2024-07-29 12:03 ` Cyril Hrubis
2024-07-29 21:29 ` Petr Vorel
2024-07-23 7:15 ` [LTP] [PATCH v2 4/7] Add ioctl_ficlone03 test Andrea Cervesato
2024-07-24 12:20 ` Cyril Hrubis
2024-07-23 7:15 ` [LTP] [PATCH v2 5/7] Add ioctl_ficlonerange01 test Andrea Cervesato
2024-07-24 15:24 ` Cyril Hrubis
2024-07-24 15:34 ` Cyril Hrubis
2024-07-23 7:15 ` [LTP] [PATCH v2 6/7] Add ioctl_ficlonerange02 test Andrea Cervesato
2024-07-24 15:37 ` Cyril Hrubis
2024-07-23 7:15 ` [LTP] [PATCH v2 7/7] Add ioctl_ficlone04 test Andrea Cervesato
2024-07-24 15:42 ` Cyril Hrubis
2024-07-24 19:36 ` Andrea Cervesato via ltp
2024-07-24 20:06 ` Cyril Hrubis
2024-07-25 7:16 ` 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=ZqIYTPN2Je61ZvOz@yuki \
--to=chrubis@suse.cz \
--cc=liwang@redhat.com \
--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