Re: Immediate fallouts from the big linux changes, and actions

[Cyril Brulebois]

Cyril Brulebois  (2023-12-24):
> Feel free to reply to this thread if you spot other fallouts.

Another FYI: one thing that I spotted early on (before realizing module
support was entirely broken), when I first diffed the list of files
available in the initramfs, building against testing's or unstable's
linux udebs: a bunch of virtio modules disappeared.

Comparing 6.5.0-5-amd64 and 6.6.8-amd64:

 usr/lib/modules/$ABI/kernel/drivers/virtio/virtio_balloon.ko
 usr/lib/modules/$ABI/kernel/drivers/virtio/virtio_dma_buf.ko
 usr/lib/modules/$ABI/kernel/drivers/virtio/virtio_input.ko
-usr/lib/modules/$ABI/kernel/drivers/virtio/virtio.ko
 usr/lib/modules/$ABI/kernel/drivers/virtio/virtio_mmio.ko
-usr/lib/modules/$ABI/kernel/drivers/virtio/virtio_pci.ko
-usr/lib/modules/$ABI/kernel/drivers/virtio/virtio_pci_legacy_dev.ko
-usr/lib/modules/$ABI/kernel/drivers/virtio/virtio_pci_modern_dev.ko
-usr/lib/modules/$ABI/kernel/drivers/virtio/virtio_ring.ko

A cursory look in linux.git didn't yield an obvious answer:

git diff debian/6.5.13-1..debian/6.6.8-1 -- debian/installer/

Indeed, that's mostly about kernel-versions's getting dropped, fuse
going away, some Depends field being updated, and some i2c-hid-* now
getting excluded in one place, and added conditionally in another one…

Searching for information about fuse and virtio, I finally noticed this
entry, which probably explains both fuse's “going away” and ditto for
some (but not all) virtio modules:

* Set CONFIG_VIRTIO_FS and its dependencies to builtin, to allow building
  images that boot directly to rootfs (skipping the initrd)

as it changes:

-CONFIG_VIRTIO_PCI=m
+CONFIG_VIRTIO_PCI=y
-CONFIG_FUSE_FS=m
+CONFIG_FUSE_FS=y
-CONFIG_VIRTIO_FS=m
+CONFIG_VIRTIO_FS=y

I thought I'd mention the answer by mail since I brought up the topic
earlier (even if only on IRC).


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Re: Immediate fallouts from the big linux changes, and actions

[Michael Tokarev]

24.12.2023 11:16, Cyril Brulebois :
...

Searching for information about fuse and virtio, I finally noticed this
entry, which probably explains both fuse's “going away” and ditto for
some (but not all) virtio modules:

 * Set CONFIG_VIRTIO_FS and its dependencies to builtin, to allow building
   images that boot directly to rootfs (skipping the initrd)

as it changes:

 -CONFIG_VIRTIO_PCI=m
 +CONFIG_VIRTIO_PCI=y
 -CONFIG_FUSE_FS=m
 +CONFIG_FUSE_FS=y
 -CONFIG_VIRTIO_FS=m
 +CONFIG_VIRTIO_FS=y


Hm. This same argument can be used to include every storage- and 
filesystem-related
module into the kernel.  Why don't we have ahci and sd_mod built-in?  This does
look quite a bit strange to me to include this stuff..

(This commit is not about big linux changes but about small debian changes ;)

/mjt

Re: Immediate fallouts from the big linux changes, and actions

[Bastian Blank]

On Sun, Dec 24, 2023 at 08:38:57AM +0100, Cyril Brulebois wrote:
> - kernel-image-* packages are now shipping /boot/vmlinuz-* (or
>   /boot/vmlinux-* depending on the arch), instead of just /boot/vmlinuz
>   (respectively /boot/vmlinux).

This was even dependent on architecture.  A lot of secondary
architectures already had various suffixes.

> - Modules are compressed now, so the drm workaround needed an updated to
>   cope with the extra .xz suffix:
> 
> https://salsa.debian.org/installer-team/debian-installer/-/commit/bd0f1106f90756e6f4514108492d71e1f2e695ea

This now hardcodes .xz.  And I'm not really sure what this does and why
this can't be fixed in the kernel packages.

> - Finally, the armel build fails because it can't find its kernel. The
>   marvell flavour seems to have been dropped entirely (at least that's
>   how I read the linux changelog for 6.6.3-1~exp1:
> 
> https://tracker.debian.org/news/1482751/accepted-linux-663-1exp1-source-into-experimental/

Yes, the kermel was broken and the checks for this disabled since quite
some time.

Bastian

-- 
Extreme feminine beauty is always disturbing.
-- Spock, "The Cloud Minders", stardate 5818.4

Re: Immediate fallouts from the big linux changes, and actions

[Cyril Brulebois]

Bastian Blank  (2023-12-24):
> On Sun, Dec 24, 2023 at 08:38:57AM +0100, Cyril Brulebois wrote:
> > - kernel-image-* packages are now shipping /boot/vmlinuz-* (or
> >   /boot/vmlinux-* depending on the arch), instead of just /boot/vmlinuz
> >   (respectively /boot/vmlinux).
> 
> This was even dependent on architecture.  A lot of secondary
> architectures already had various suffixes.

Looking at kernel-image-* 6.5.13-1 for release archs, I'm only seeing
mips64el (-6.5.0-5-5kc-malta, -6.5.0-5-loongson-3, -6.5.0-5-mips64r2el
suffixes), and its build targets didn't hit the codepath I had to patch
for the general case.

Anyway, since you're not reacting with “oops, we didn't mean to”, I'm
going to count this as a deliberate change.

> > - Modules are compressed now, so the drm workaround needed an updated to
> >   cope with the extra .xz suffix:
> > 
> > https://salsa.debian.org/installer-team/debian-installer/-/commit/bd0f1106f90756e6f4514108492d71e1f2e695ea
> 
> This now hardcodes .xz.  And I'm not really sure what this does and why
> this can't be fixed in the kernel packages.

Because that's a workaround for a problem that's not in the kernel and
that remains to be fully investigated.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature