Bug 1090009 - Broken supported.conf leading to unusuable kernel-default-base
Broken supported.conf leading to unusuable kernel-default-base
Status: RESOLVED FIXED
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Kernel
Current
Other Other
: P5 - None : Major (vote)
: ---
Assigned To: E-mail List
E-mail List
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-04-18 09:18 UTC by Fabian Vogt
Modified: 2018-04-18 12:40 UTC (History)
4 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fabian Vogt 2018-04-18 09:18:22 UTC
supported.conf in the kernel-source master branch is totally out of date and not in sync with the SLE15 supported.conf.

This leads to a kernel-default-base which doesn't boot (no btrfs, for example).

The list also includes nonexisting modules, e.g. fs/overlayfs/overlayfs.

I tried to merge the SLE15 and master supported.conf with scripts/supported-conf-fixup, but the diff contains changes I'm not familiar with.
Comment 1 Michal Kubeček 2018-04-18 09:28:43 UTC
For openSUSE kernels, the only interesting lines should those marked with

  +base
  +${name}-kmp

as those define what should go into kernel-${flavor}-base and KMPs named
${name}-kmp-${flavor}. The rest doesn't really matter.
Comment 2 Thorsten Kukuk 2018-04-18 09:43:31 UTC
The openSUSE kernels should be compareable with the SLES kernels, else Factory cannot be used for Factory First and nother development for SLES features.

In this case, kernel-default-base is critical for all MicroOS/CaaSP related work.
Comment 3 Fabian Vogt 2018-04-18 11:18:44 UTC
(In reply to Michal Kubeček from comment #1)
> For openSUSE kernels, the only interesting lines should those marked with
> 
>   +base
>   +${name}-kmp
> 
> as those define what should go into kernel-${flavor}-base and KMPs named
> ${name}-kmp-${flavor}. The rest doesn't really matter.

Ok, that means I can copy over the supported.conf from SLE15 to master and make sure that the +.*-kmp lines stay the same?
Comment 4 Michal Kubeček 2018-04-18 12:06:29 UTC
I believe so. The primary purpose of supported.conf is to distinguish between
supported (normal lines) and unsupported (line starting with "-" or module not
listed) modules in SLE. In openSUSE, this is ignored.

Then there are lines with "+base" marker, these modules go into
kernel-${flavor}-base packages. This is probably the only part interesting for
openSUSE builds.

Modules marked with "+${name}-kmp" marker are packaged into KMP named
${name}-kmp. At the moment, there don't seem to be any in master and stable
branches which is probably what we want. These KMPs are built from standard
kernel sources but packaged separately so that they can be provided only in
addon products (e.g. HAE). In openSUSE, there is little reason not to include
them in the main package.

As SLE15 supported.conf has been reviewed recently but very little care is
taken in master/stable, IMHO the best course of action would be to simply
copy the SLE15 version and remove all "+${name}-kmp" markers. And maybe add
some modules which we want in kernel-${flavor}-base but which do not exist
(or are not built) in SLE15 - if there are such modules.

Let's ask another Michal to be sure.
Comment 5 Michal Suchanek 2018-04-18 12:14:36 UTC
Just copy the supported.conf from SLE15 (or openSUSE 15) and if it works for you that's fine.

Only the +base should be used on openSUSE.
Comment 6 Michal Suchanek 2018-04-18 12:21:29 UTC
submitted the update for master

Should be fixed in 4.17
Comment 7 Fabian Vogt 2018-04-18 12:25:38 UTC
(In reply to Michal Suchanek from comment #6)
> submitted the update for master
> 
> Should be fixed in 4.17

Oh, I was just about to do it as well - in fact a test kernel is building.

Anyway, I compared our commits and I found that you didn't remove the -kmp markers, intentional?
Comment 8 Michal Suchanek 2018-04-18 12:40:55 UTC
Yes, they should be ignored. If they break something it will be broken on Leap 15 which merges the supported.conf directly from SLE15.