From: Mauro Carvalho Chehab <firstname.lastname@example.org> To: Greg Kroah-Hartman <email@example.com> Cc: Tony Battersby <firstname.lastname@example.org>, Jiri Slaby <email@example.com>, firstname.lastname@example.org, Jari Ruusu <email@example.com>, David Laight <David.Laight@aculab.com>, Christoph Biedl <firstname.lastname@example.org>, email@example.com Subject: Re: Kernel version numbers after 4.9.255 and 4.4.255 Date: Sat, 6 Feb 2021 10:24:02 +0100 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <YB5DTUiurAwqZbz1@kroah.com> Em Sat, 6 Feb 2021 08:20:45 +0100 Greg Kroah-Hartman <email@example.com> escreveu: > On Fri, Feb 05, 2021 at 07:11:05PM +0100, Mauro Carvalho Chehab wrote: > > Em Fri, 5 Feb 2021 12:31:05 -0500 > > Tony Battersby <firstname.lastname@example.org> escreveu: > > > > > On 2/4/21 6:00 AM, Jiri Slaby wrote: > > > > Agreed. But currently, sublevel won't "wrap", it will "overflow" to > > > > patchlevel. And that might be a problem. So we might need to update the > > > > header generation using e.g. "sublevel & 0xff" (wrap around) or > > > > "sublevel > 255 : 255 : sublevel" (be monotonic and get stuck at 255). > > > > > > > > In both LINUX_VERSION_CODE generation and KERNEL_VERSION proper. > > > > > > My preference would be to be monotonic and get stuck at 255 to avoid > > > breaking out-of-tree modules. If needed, add another macro that > > > increases the number of bits that can be used to check for sublevels > > > > 255, while keeping the old macros for compatibility reasons. Since > > > sublevels > 255 have never existed before, any such checks must be > > > newly-added, so they can be required to use the new macros. > > > > > > I do not run the 4.4/4.9 kernels usually, but I do sometimes test a wide > > > range of kernels from 3.18 (gasp!) up to the latest when bisecting, > > > benchmarking, or debugging problems. And I use a number of out-of-tree > > > modules that rely on the KERNEL_VERSION to make everything work. Some > > > out-of-tree modules like an updated igb network driver might be needed > > > to make it possible to test the old kernel on particular hardware. > > > > > > In the worst case, I can patch LINUX_VERSION_CODE and KERNEL_VERSION > > > locally to make out-of-tree modules work. Or else just not test kernels > > > with sublevel > 255. > > > > Overflowing LINUX_VERSION_CODE breaks media applications. Several media > > APIs have an ioctl that returns the Kernel version: > > > > drivers/media/cec/core/cec-api.c: caps.version = LINUX_VERSION_CODE; > > drivers/media/mc/mc-device.c: info->media_version = LINUX_VERSION_CODE; > > drivers/media/v4l2-core/v4l2-ioctl.c: cap->version = LINUX_VERSION_CODE; > > drivers/media/v4l2-core/v4l2-subdev.c: cap->version = LINUX_VERSION_CODE; > > This always struck me as odd, because why can't they just use the > uname(2) syscall instead? I agree that this is odd on upstream Kernels. On backported ones, this should be filled with the version of the V4L2 core. We maintain a tree that allows running older Kernels with the latest V4L2 media drivers and subsystem. On such tree, there's a patch that replaces LINUX_VERSION_CODE macro to V4L2_VERSION: https://git.linuxtv.org/media_build.git/tree/backports/api_version.patch There's a logic here which gets the version of the V4L2 used at the build. So, right now, it is filled with: #define V4L2_VERSION 330496 /* 0x050b00 */ In other words, even if you run the backported driver on, let's say, Kernel 4.8, those calls will tell that the driver's version is from Kernel 5.11. - Providing a little of history behind those, this came together with the V4L version 2 API developed during Kernel 2.5.x and merged at Kernel 2.6.0. When such API was originally introduced, this field was meant to contain the driver's version. The problem is that people used to change the drivers (even with major rewrites) without changing its version. We ended by standardizing it everywhere, filling those at the media core, instead of doing it at driver's level - and using the Kernel version. This way, developers won't need to be concerned of keeping this updated as the subsystem evolves. With time, we also improved the V4L2 API in a way that applications can be able to directly detect the core/driver functionalities without needing to rely on such fields. So, I guess recent versions of most open source applications nowadays don't use it. > > Those can be used by applications in order to enable some features that > > are available only after certain Kernel versions. > > > > This is somewhat deprecated, in favor of the usage of some other > > capability fields, but for instance, the v4l2-compliance userspace tool > > have two such checks: > > > > utils/v4l2-compliance/v4l2-compliance.cpp > > 640: fail_on_test((vcap.version >> 16) < 3); > > 641: if (vcap.version >= 0x050900) // Present from 5.9.0 onwards > > > > As far as I remember, all such checks are against major.minor. So, > > something like: > > > > sublevel = (sublevel > 0xff) ? 0xff : sublevel; > > > > inside KERNEL_VERSION macro should fix such regression at -stable. > > I think if we clamp KERNEL_VERSION at 255 we should be fine for anyone > checking this type of thing. Sasha has posted patches to do this. Yes, this should be enough. As far as I remember, when opensource apps use the version from the API, since Kernel 3.0, they always check only for major.minor. So, the only problem with those APIs are due to overflows. Setting sublevel to any value beteen 0-255 should work, from V4L2 API standpoint. Thanks, Mauro
next prev parent reply other threads:[~2021-02-06 9:25 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-04 5:59 Jari Ruusu 2021-02-04 6:20 ` Greg Kroah-Hartman 2021-02-04 7:26 ` Jiri Slaby 2021-02-04 8:51 ` Greg Kroah-Hartman 2021-02-04 11:00 ` Jiri Slaby 2021-02-04 16:28 ` David Laight 2021-02-04 16:48 ` Greg Kroah-Hartman 2021-02-04 20:19 ` Christoph Biedl 2021-02-05 6:52 ` Greg KH 2021-02-05 17:31 ` Tony Battersby 2021-02-05 18:11 ` Mauro Carvalho Chehab 2021-02-06 7:20 ` Greg Kroah-Hartman 2021-02-06 9:24 ` Mauro Carvalho Chehab [this message] 2021-02-06 9:29 ` Greg Kroah-Hartman 2021-02-06 9:48 ` Mauro Carvalho Chehab 2021-02-06 10:18 ` Hans Verkuil 2021-02-06 11:18 ` Mauro Carvalho Chehab 2021-02-06 7:22 ` Greg Kroah-Hartman 2021-02-05 9:06 ` Pavel Machek 2021-02-05 9:33 ` Greg Kroah-Hartman 2021-02-05 18:44 ` Pavel Machek 2021-02-06 7:23 ` Greg Kroah-Hartman
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 \ --email@example.com \ --firstname.lastname@example.org \ --cc=David.Laight@aculab.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Kernel version numbers after 4.9.255 and 4.4.255' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).