From: Jason Gunthorpe <jgg@nvidia.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Cédric Le Goater" <clg@redhat.com>,
"Shameer Kolothum" <skolothumtho@nvidia.com>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org,
eric.auger@redhat.com, alex@shazbot.org, cohuck@redhat.com,
mst@redhat.com, nicolinc@nvidia.com, nathanc@nvidia.com,
mochs@nvidia.com, jonathan.cameron@huawei.com,
zhenzhong.duan@intel.com, vivek.kasireddy@intel.com,
kjaju@nvidia.com, "Jason Wang" <jasowang@redhat.com>
Subject: Re: [PATCH v4 1/3] linux-headers: Update to Linux v6.19-rc1
Date: Wed, 21 Jan 2026 13:12:48 -0400 [thread overview]
Message-ID: <20260121171248.GH1134360@nvidia.com> (raw)
In-Reply-To: <CAFEAcA9+kp7K4cGeMx2PTGp1V3SkKoqyHEOZhFD-QQ2Y4WZHPQ@mail.gmail.com>
On Wed, Jan 21, 2026 at 02:21:17PM +0000, Peter Maydell wrote:
> But it looks to me like this is a bug in the Linux headers:
> they seem to have changed in a non-backwards compatible way,
> and possibly even in a way that makes it not possible for
> userspace code to use ifdefs to handle "maybe the header
> is the old version or the new version".
Technically Linux doesn't provide an API guarentee, just an ABI
guarentee.
Ie we don't guarentee all old userspace compiles with the new headers,
we just guarentee that once compiled it keeps working..
You need to use something like configure and compile trial tests to
figure things out.
IMHO this happens rarely enough that what is proposed here as a single
patch is the best option.
Jason
next prev parent reply other threads:[~2026-01-21 17:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 11:41 [PATCH v4 0/3] vfio: Add DMABUF support for PCI BAR regions Shameer Kolothum
2026-01-21 11:41 ` [PATCH v4 1/3] linux-headers: Update to Linux v6.19-rc1 Shameer Kolothum
2026-01-21 14:00 ` Cédric Le Goater
2026-01-21 14:21 ` Peter Maydell
2026-01-21 17:12 ` Jason Gunthorpe [this message]
2026-01-23 14:26 ` Cédric Le Goater
2026-01-21 11:41 ` [PATCH v4 2/3] hw/vfio: Add helper to retrieve device feature Shameer Kolothum
2026-01-21 11:41 ` [PATCH v4 3/3] hw/vfio/region: Create dmabuf for PCI BAR per region Shameer Kolothum
2026-01-21 12:36 ` [PATCH v4 0/3] vfio: Add DMABUF support for PCI BAR regions Michael S. Tsirkin
2026-01-21 12:49 ` Eric Auger
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=20260121171248.GH1134360@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex@shazbot.org \
--cc=clg@redhat.com \
--cc=cohuck@redhat.com \
--cc=eric.auger@redhat.com \
--cc=jasowang@redhat.com \
--cc=jonathan.cameron@huawei.com \
--cc=kjaju@nvidia.com \
--cc=mochs@nvidia.com \
--cc=mst@redhat.com \
--cc=nathanc@nvidia.com \
--cc=nicolinc@nvidia.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=skolothumtho@nvidia.com \
--cc=vivek.kasireddy@intel.com \
--cc=zhenzhong.duan@intel.com \
/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.