From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: ltp@lists.linux.it, Fabrice Fontaine <fontaine.fabrice@gmail.com>
Subject: Re: [LTP] [PATCH] configure.ac: fix mount_attr detection
Date: Fri, 10 Mar 2023 12:42:49 +0100 [thread overview]
Message-ID: <20230310114249.GB22294@pevik> (raw)
In-Reply-To: <CAEemH2eBqt1_ZTY3GCRfgx4EQdWiJJepA_wVGpSg6=pYubHddw@mail.gmail.com>
Hi Li,
> On Fri, Mar 10, 2023 at 5:31 PM Petr Vorel <pvorel@suse.cz> wrote:
> > Hi all,
> > ...
> > > > I wonder if we can get this whole mess of two different fallback
> > headers
> > > > simplified. Looking at the glibc implementation it seems to include
> > > > "linux/mount.h" if it does exist. So most reasonable solution would do
> > > > the same I guess which we did before the commit you reference.
> > > This is indeed correct if only face the latest Glibc, but that might have
> > > problems when building LTP on a middle version of Glibc/Kernel-headers.
> > > The bug I mentioned in the last email was fixed since glibc-2.37~426.
> > Do you know which exact commit has fixed it? It'd help us to realize when
> > this
> > fix is not needed any more (it'd be good to put it into the commit
> > message).
> I mean this commit:
> https://github.com/kraj/glibc/commit/774058d72942249f71d74e7f2b639f77184160a6
Thanks for info. Fix from 2.37, it was also cherry picked to release/2.36/master
branch, but not to branches for older releases (2.35 and 2.34).
I suppose there will be always some toolchain/distro with older glibc without
this fix, thus I'd merge it now, and made simplification Cyril suggested
sometimes next year.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-03-10 11:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-26 19:25 [LTP] [PATCH] configure.ac: fix mount_attr detection Fabrice Fontaine
2023-02-27 11:28 ` Cyril Hrubis
2023-03-09 10:56 ` Petr Vorel
2023-03-09 13:09 ` Li Wang
2023-03-09 13:00 ` Li Wang
2023-03-10 6:25 ` Li Wang
2023-03-10 9:31 ` Petr Vorel
2023-03-10 9:42 ` Li Wang
2023-03-10 11:42 ` Petr Vorel [this message]
2023-03-20 14:59 ` Petr Vorel
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=20230310114249.GB22294@pevik \
--to=pvorel@suse.cz \
--cc=fontaine.fabrice@gmail.com \
--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