From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 1/7] Add fallback definitions for lapi/fs.h
Date: Thu, 25 Jul 2024 17:17:24 +0200 [thread overview]
Message-ID: <ZqJshM8YUQKwLR5s@yuki> (raw)
In-Reply-To: <20240725125516.GA987417@pevik>
Hi!
> > 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.
>
> Hm, it makes sense to keep it. But nobody will remember once we raise the
> support.
Maybe we should at least add a comment glibc-2.22 workaround or
something that could be found with grep.
> Also, removing HAVE_LINUX_FS_H [1] works in the CI [2], including distros with
> glibc 2.36 (minimal build [3] or all cross-compile builds, e.g. [4]).
>
> I wonder how realistic is that somebody is still affected by this issue.
That's a good question but I'm afraid the only way to find out is to
remove the workaround and wait for people complain that the next LTP
release is broken...
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-07-25 15:18 UTC|newest]
Thread overview: 29+ 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
2024-07-25 12:55 ` Petr Vorel
2024-07-25 15:17 ` Cyril Hrubis [this message]
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 11:53 ` Petr Vorel
2024-07-29 12:03 ` Cyril Hrubis
2024-07-29 12:03 ` Cyril Hrubis
2024-07-29 21:29 ` Petr Vorel
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=ZqJshM8YUQKwLR5s@yuki \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=pvorel@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.