Linux Test Project
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Jan Stancek <jstancek@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/2] configure: Fix build on kernel 6.14 headers
Date: Wed, 4 Jun 2025 16:30:25 +0200	[thread overview]
Message-ID: <20250604143025.GA1128251@pevik> (raw)
In-Reply-To: <CAASaF6yU+s4ZHgSU5mvb+R4cZiamqqM0eN6sHQVTHH0TEP6uug@mail.gmail.com>

Hi all,

> On Tue, Jun 3, 2025 at 6:12 PM Petr Vorel <pvorel@suse.cz> wrote:

> > Hi all,

> > > Hi!
> > > Let's push this now, it's simple enough and fixes the CI.

> > I'm sorry, it did not fix the problem due the old problem of indirect include
> > <linux/mount.h> by <linux/fs.h> on Alpine v3.22 (the default Alpine version in
> > GitHub action), which uses 6.14.2 kernel headers:

> >     In file included from /usr/include/linux/fs.h:19,
> >                      from /usr/include/linux/btrfs.h:29,
> >                      from statmount02.c:23:

> from statmount02.c:

> The btrfs validation is currently skipped due to the lack of support for VFS
> ...
> #include <linux/btrfs.h>

> Does the test actually need linux/btrfs.h ?

Jan, very good point, it really was not needed. Removal merged as fe8c0dac5a,
thank you!

> > I suppose we should have 2 or 3 lapi files:

> > 1) lapi/mount.h
> > mount definitions (guarded by #ifndef) - the old ones from <sys/mount.h> e.g.
> > MS_REC, MS_PRIVATE and probably the new ones from <linux/mount.h>, e.g.
> > MNT_ID_REQ_SIZE_VER0. None of <sys/mount.h> <linux/mount.h> should be included
> > in it.

> > 2) lapi/linux_mount.h
> > mount structs (nowadays vast majority if not all from <linux/mount.h> only).
> > This header can include <linux/mount.h> and lapi/mount.h.
> > That allows to have configure.ac to safely use <linux/mount.h> for detection.

> > 3) lapi/sys_mount.h
> > Optional helper header which would include lapi/mount.h and <sys/mount.h>
> > (to keep the current approach that lapi headers include system headers so that
> > tests does not need to do it.

I'll be pragmatic and although the above would be an improvement, I'll postpone
doing it until it's really needed.

Kind regards,
Petr

> > WDYT?

> > Kind regards,
> > Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

      reply	other threads:[~2025-06-04 14:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-02 17:08 [LTP] [PATCH 1/2] configure: Fix build on kernel 6.14 headers Petr Vorel
2025-06-02 17:08 ` [LTP] [PATCH 2/2] lapi/mount.h: Add missing mnt_ns_id member Petr Vorel
2025-06-24  9:20   ` Andrea Cervesato via ltp
2025-06-03 10:35 ` [LTP] [PATCH 1/2] configure: Fix build on kernel 6.14 headers Cyril Hrubis
2025-06-03 12:36   ` Jan Stancek via ltp
2025-06-03 12:40     ` Petr Vorel
2025-06-03 16:11   ` Petr Vorel
2025-06-04  8:39     ` Li Wang via ltp
2025-06-04 13:13     ` Jan Stancek via ltp
2025-06-04 14:30       ` 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=20250604143025.GA1128251@pevik \
    --to=pvorel@suse.cz \
    --cc=jstancek@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