Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #66007 > unrolled thread

Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_N1a1Mk/lib/modules/5.4.0-1-amd64/modules.builtin.bin'

Started byBenjamin Poirier <benjamin.poirier@gmail.com>
First post2020-01-07 02:00 +0100
Last post2020-01-08 16:10 +0100
Articles 5 — 2 participants

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_N1a1Mk/lib/modules/5.4.0-1-amd64/modules.builtin.bin' Benjamin Poirier <benjamin.poirier@gmail.com> - 2020-01-07 02:00 +0100
    Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_N1a1Mk/lib/modules/5.4.0-1-amd64/modules.builtin.bin' Benjamin Poirier <benjamin.poirier@gmail.com> - 2020-01-08 01:30 +0100
      Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_N1a1Mk/lib/modules/5.4.0-1-amd64/modules.builtin.bin' Salvatore Bonaccorso <carnil@debian.org> - 2020-01-08 13:10 +0100
        Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_N1a1Mk/lib/modules/5.4.0-1-amd64/modules.builtin.bin' Salvatore Bonaccorso <carnil@debian.org> - 2020-01-08 13:50 +0100
          Bug#948427: modules.builtin.modinfo not included in signed image packages Salvatore Bonaccorso <carnil@debian.org> - 2020-01-08 16:10 +0100

#66007 — Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_N1a1Mk/lib/modules/5.4.0-1-amd64/modules.builtin.bin'

FromBenjamin Poirier <benjamin.poirier@gmail.com>
Date2020-01-07 02:00 +0100
SubjectBug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_N1a1Mk/lib/modules/5.4.0-1-amd64/modules.builtin.bin'
Message-ID<zlLnX-3Fl-1@gated-at.bofh.it>
I'm not sure if it's related but I saw almost the same error on last
upgrade (but for 5.4.0-2):

depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_J2sneW/lib/modules/5.4.0-2-amd64/modules.builtin.bin'

and I now get:

root@vsid:~# lttng list --kernel
Error: Unable to list kernel events: Kernel tracer not available
root@vsid:~# journalctl -u lttng-sessiond.service
[...]
Jan 07 09:33:20 vsid lttng-sessiond[403]: Error: Failed to load kmod library resources
Jan 07 09:33:20 vsid lttng-sessiond[403]: Warning: No kernel tracer available

lttng-modules-dkms is installed. I can load the modules manually but I
still get the same error.

[toc] | [next] | [standalone]

#66026

FromBenjamin Poirier <benjamin.poirier@gmail.com>
Date2020-01-08 01:30 +0100
Message-ID<zm7ou-vE-3@gated-at.bofh.it>
In reply to#66007
On 2020/01/07 10:12, Michael Jeanson wrote:
> On 2020-01-06 7:46 p.m., Benjamin Poirier wrote:
> > I'm not sure if it's related but I saw almost the same error on last
> > upgrade (but for 5.4.0-2):
> > 
> > depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_J2sneW/lib/modules/5.4.0-2-amd64/modules.builtin.bin'
> > 
> > and I now get:
> > 
> > root@vsid:~# lttng list --kernel
> > Error: Unable to list kernel events: Kernel tracer not available
> > root@vsid:~# journalctl -u lttng-sessiond.service
> > [...]
> > Jan 07 09:33:20 vsid lttng-sessiond[403]: Error: Failed to load kmod library resources
> > Jan 07 09:33:20 vsid lttng-sessiond[403]: Warning: No kernel tracer available
> > 
> > lttng-modules-dkms is installed. I can load the modules manually but I
> > still get the same error.
> > 
> 
> Hi,
> 
> If you had just installed the lttng-modules-dkms and lttng-tools packages,
> it's possible that the lttng-sessiond deamon was started before the kernel
> modules were built and so it couldn't load them.

Looks like the modules are built before lttng-sessiond is started:
	Setting up lttng-modules-dkms (2.11.0-2) ...
	Loading new lttng-modules-2.11.0 DKMS files...
	Building for 5.4.0-2-amd64
	Building initial module for 5.4.0-2-amd64
	Done.

	lttng-lib-ring-buffer.ko:
	Running module version sanity check.
	 - Original module
	   - No original module exists within this kernel
	 - Installation
	   - Installing to /lib/modules/5.4.0-2-amd64/updates/dkms/

	[...]

	depmod...

	DKMS: install completed.
	Setting up linux-headers-5.4.0-2-amd64 (5.4.8-1) ...
	/etc/kernel/header_postinst.d/dkms:
	dkms: running auto installation service for kernel 5.4.0-2-amd64:.
	Setting up sudo (1.8.29-1) ...
	Setting up babeltrace (1.5.7-2) ...
	Setting up liburcu6:amd64 (0.11.1-2) ...
	Setting up linux-headers-amd64 (5.4.8-1) ...
	Setting up liblttng-ctl0:amd64 (2.11.0-3) ...
	Setting up lttng-tools (2.11.0-3) ...

Still, it doesn't work.

> Simply restarting the sessiond should fix this.

I tried restarting lttng-sessiond or rebooting the machine but it was no
help, lttng-sessiond always reports:
	Error: Failed to load kmod library resources
	Warning: No kernel tracer available

A quick look into the code shows that is:
src/bin/lttng-sessiond/modprobe.c
	kmod_set_log_fn(*ctx, log_kmod, NULL);
	ret = kmod_load_resources(*ctx);
	if (ret < 0) {
		ERR("Failed to load kmod library resources");
		goto error;
	}

I didn't dig into libkmod, but I noticed (using opensnoop.bt) the
following:
	8071   lttng-sessiond      2   0 /lib/modules/5.4.0-2-amd64/modules.dep.bin
	8071   lttng-sessiond      2   0 /lib/modules/5.4.0-2-amd64/modules.alias.bin
	8071   lttng-sessiond      2   0 /lib/modules/5.4.0-2-amd64/modules.symbols.bin
	8071   lttng-sessiond      2   0 /lib/modules/5.4.0-2-amd64/modules.builtin.alias.bin

On another machine which I haven't yet updated and where lttng still
works, I see:
	193519 lttng-sessiond      2   0 /lib/modules/5.4.0-1-amd64/modules.dep.bin
	193519 lttng-sessiond      2   0 /lib/modules/5.4.0-1-amd64/modules.alias.bin
	193519 lttng-sessiond      2   0 /lib/modules/5.4.0-1-amd64/modules.symbols.bin
	193519 lttng-sessiond      2   0 /lib/modules/5.4.0-1-amd64/modules.builtin.bin

Not sure if /lib/modules/5.4.0-2-amd64/modules.builtin.alias.bin is
relevant but it's an empty file...

After downgrading libkmod2 from
	Version: 26+20191223-1
to
	Version: 26-3
the issue with lttng is no longer apparent:
	root@vsid:/tmp# lttng list --kernel
	Kernel events:
	-------------
	      asoc_snd_soc_bias_level_start (loglevel: TRACE_EMERG (0)) (type: tracepoint)
	      asoc_snd_soc_bias_level_done (loglevel: TRACE_EMERG (0)) (type: tracepoint)
	      asoc_snd_soc_dapm_start (loglevel: TRACE_EMERG (0)) (type: tracepoint)
	[...]

[toc] | [prev] | [next] | [standalone]

#66030

FromSalvatore Bonaccorso <carnil@debian.org>
Date2020-01-08 13:10 +0100
Message-ID<zmijT-7ly-5@gated-at.bofh.it>
In reply to#66026
Hi Benjamin,

On Wed, Jan 08, 2020 at 09:24:30AM +0900, Benjamin Poirier wrote:
[...]
> Looks like the modules are built before lttng-sessiond is started:
> 	Setting up lttng-modules-dkms (2.11.0-2) ...
> 	Loading new lttng-modules-2.11.0 DKMS files...
> 	Building for 5.4.0-2-amd64
> 	Building initial module for 5.4.0-2-amd64
> 	Done.
> 
> 	lttng-lib-ring-buffer.ko:
> 	Running module version sanity check.
> 	 - Original module
> 	   - No original module exists within this kernel
> 	 - Installation
> 	   - Installing to /lib/modules/5.4.0-2-amd64/updates/dkms/
> 
> 	[...]
> 
> 	depmod...
> 
> 	DKMS: install completed.
> 	Setting up linux-headers-5.4.0-2-amd64 (5.4.8-1) ...
> 	/etc/kernel/header_postinst.d/dkms:
> 	dkms: running auto installation service for kernel 5.4.0-2-amd64:.
> 	Setting up sudo (1.8.29-1) ...
> 	Setting up babeltrace (1.5.7-2) ...
> 	Setting up liburcu6:amd64 (0.11.1-2) ...
> 	Setting up linux-headers-amd64 (5.4.8-1) ...
> 	Setting up liblttng-ctl0:amd64 (2.11.0-3) ...
> 	Setting up lttng-tools (2.11.0-3) ...
> 
> Still, it doesn't work.
> 
> > Simply restarting the sessiond should fix this.
> 
> I tried restarting lttng-sessiond or rebooting the machine but it was no
> help, lttng-sessiond always reports:
> 	Error: Failed to load kmod library resources
> 	Warning: No kernel tracer available
> 
> A quick look into the code shows that is:
> src/bin/lttng-sessiond/modprobe.c
> 	kmod_set_log_fn(*ctx, log_kmod, NULL);
> 	ret = kmod_load_resources(*ctx);
> 	if (ret < 0) {
> 		ERR("Failed to load kmod library resources");
> 		goto error;
> 	}
> 
> I didn't dig into libkmod, but I noticed (using opensnoop.bt) the
> following:
> 	8071   lttng-sessiond      2   0 /lib/modules/5.4.0-2-amd64/modules.dep.bin
> 	8071   lttng-sessiond      2   0 /lib/modules/5.4.0-2-amd64/modules.alias.bin
> 	8071   lttng-sessiond      2   0 /lib/modules/5.4.0-2-amd64/modules.symbols.bin
> 	8071   lttng-sessiond      2   0 /lib/modules/5.4.0-2-amd64/modules.builtin.alias.bin
> 
> On another machine which I haven't yet updated and where lttng still
> works, I see:
> 	193519 lttng-sessiond      2   0 /lib/modules/5.4.0-1-amd64/modules.dep.bin
> 	193519 lttng-sessiond      2   0 /lib/modules/5.4.0-1-amd64/modules.alias.bin
> 	193519 lttng-sessiond      2   0 /lib/modules/5.4.0-1-amd64/modules.symbols.bin
> 	193519 lttng-sessiond      2   0 /lib/modules/5.4.0-1-amd64/modules.builtin.bin
> 
> Not sure if /lib/modules/5.4.0-2-amd64/modules.builtin.alias.bin is
> relevant but it's an empty file...
> 
> After downgrading libkmod2 from
> 	Version: 26+20191223-1
> to
> 	Version: 26-3
> the issue with lttng is no longer apparent:
> 	root@vsid:/tmp# lttng list --kernel
> 	Kernel events:
> 	-------------
> 	      asoc_snd_soc_bias_level_start (loglevel: TRACE_EMERG (0)) (type: tracepoint)
> 	      asoc_snd_soc_bias_level_done (loglevel: TRACE_EMERG (0)) (type: tracepoint)
> 	      asoc_snd_soc_dapm_start (loglevel: TRACE_EMERG (0)) (type: tracepoint)
> 	[...] 
> 

Should we track this in a separate bug from #948257?

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#66032

FromSalvatore Bonaccorso <carnil@debian.org>
Date2020-01-08 13:50 +0100
Message-ID<zmiWB-7yR-1@gated-at.bofh.it>
In reply to#66030
Hi Benjamin,

On Wed, Jan 08, 2020 at 01:07:20PM +0100, Salvatore Bonaccorso wrote:
> Hi Benjamin,
> 
> On Wed, Jan 08, 2020 at 09:24:30AM +0900, Benjamin Poirier wrote:
> [...]
> > Looks like the modules are built before lttng-sessiond is started:
> > 	Setting up lttng-modules-dkms (2.11.0-2) ...
> > 	Loading new lttng-modules-2.11.0 DKMS files...
> > 	Building for 5.4.0-2-amd64
> > 	Building initial module for 5.4.0-2-amd64
> > 	Done.
> > 
> > 	lttng-lib-ring-buffer.ko:
> > 	Running module version sanity check.
> > 	 - Original module
> > 	   - No original module exists within this kernel
> > 	 - Installation
> > 	   - Installing to /lib/modules/5.4.0-2-amd64/updates/dkms/
> > 
> > 	[...]
> > 
> > 	depmod...
> > 
> > 	DKMS: install completed.
> > 	Setting up linux-headers-5.4.0-2-amd64 (5.4.8-1) ...
> > 	/etc/kernel/header_postinst.d/dkms:
> > 	dkms: running auto installation service for kernel 5.4.0-2-amd64:.
> > 	Setting up sudo (1.8.29-1) ...
> > 	Setting up babeltrace (1.5.7-2) ...
> > 	Setting up liburcu6:amd64 (0.11.1-2) ...
> > 	Setting up linux-headers-amd64 (5.4.8-1) ...
> > 	Setting up liblttng-ctl0:amd64 (2.11.0-3) ...
> > 	Setting up lttng-tools (2.11.0-3) ...
> > 
> > Still, it doesn't work.
> > 
> > > Simply restarting the sessiond should fix this.
> > 
> > I tried restarting lttng-sessiond or rebooting the machine but it was no
> > help, lttng-sessiond always reports:
> > 	Error: Failed to load kmod library resources
> > 	Warning: No kernel tracer available
> > 
> > A quick look into the code shows that is:
> > src/bin/lttng-sessiond/modprobe.c
> > 	kmod_set_log_fn(*ctx, log_kmod, NULL);
> > 	ret = kmod_load_resources(*ctx);
> > 	if (ret < 0) {
> > 		ERR("Failed to load kmod library resources");
> > 		goto error;
> > 	}
> > 
> > I didn't dig into libkmod, but I noticed (using opensnoop.bt) the
> > following:
> > 	8071   lttng-sessiond      2   0 /lib/modules/5.4.0-2-amd64/modules.dep.bin
> > 	8071   lttng-sessiond      2   0 /lib/modules/5.4.0-2-amd64/modules.alias.bin
> > 	8071   lttng-sessiond      2   0 /lib/modules/5.4.0-2-amd64/modules.symbols.bin
> > 	8071   lttng-sessiond      2   0 /lib/modules/5.4.0-2-amd64/modules.builtin.alias.bin
> > 
> > On another machine which I haven't yet updated and where lttng still
> > works, I see:
> > 	193519 lttng-sessiond      2   0 /lib/modules/5.4.0-1-amd64/modules.dep.bin
> > 	193519 lttng-sessiond      2   0 /lib/modules/5.4.0-1-amd64/modules.alias.bin
> > 	193519 lttng-sessiond      2   0 /lib/modules/5.4.0-1-amd64/modules.symbols.bin
> > 	193519 lttng-sessiond      2   0 /lib/modules/5.4.0-1-amd64/modules.builtin.bin
> > 
> > Not sure if /lib/modules/5.4.0-2-amd64/modules.builtin.alias.bin is
> > relevant but it's an empty file...
> > 
> > After downgrading libkmod2 from
> > 	Version: 26+20191223-1
> > to
> > 	Version: 26-3
> > the issue with lttng is no longer apparent:
> > 	root@vsid:/tmp# lttng list --kernel
> > 	Kernel events:
> > 	-------------
> > 	      asoc_snd_soc_bias_level_start (loglevel: TRACE_EMERG (0)) (type: tracepoint)
> > 	      asoc_snd_soc_bias_level_done (loglevel: TRACE_EMERG (0)) (type: tracepoint)
> > 	      asoc_snd_soc_dapm_start (loglevel: TRACE_EMERG (0)) (type: tracepoint)
> > 	[...] 
> > 
> 
> Should we track this in a separate bug from #948257?

So here is what I think is part of what is going on (unless there is
something broken in my analysis):

Since 898490c010b5 ("moduleparam: Save information about built-in
modules in separate file")[1] which is in 5.2-rc1, there is a new
modules.builtin.modinfo provided.

 [1]: <https://git.kernel.org/linus/898490c010b5d2e499e03b7e815fc214209ac583>

This one is installed in the -unsigned binary packages but not copied
over into the signing template, so the signed linux image packages do
not contain it.

Now with kmod/26+20191223-1 we have 60084cf1cb24 ("libkmod: Add parser
for modules.builtin.modinfo")[2] adding the parser and [3] and [4]
using that.

 [2]: <https://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git/commit/?id=60084cf1cb24dc3a257976c0d539a4c3ffda5db5>
 [3]: <https://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git/commit/?id=73eed2aba3cbe18bbda40f18f7bc32e8de1ec81f>
 [4]: <https://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git/commit/?id=b866b2165ae6cf18fb26b635f4a7ee57c0334731>

Salvatore

[toc] | [prev] | [next] | [standalone]

#66035 — Bug#948427: modules.builtin.modinfo not included in signed image packages

FromSalvatore Bonaccorso <carnil@debian.org>
Date2020-01-08 16:10 +0100
SubjectBug#948427: modules.builtin.modinfo not included in signed image packages
Message-ID<zml86-Bw-7@gated-at.bofh.it>
In reply to#66032
Source: linux
Version: 5.2.6-1
Tags: patch
X-Debbugs-CC: Benjamin Poirier <benjamin.poirier@gmail.com>,Michael Jeanson <mjeanson@debian.org>

As reported in originally https://bugs.debian.org/948257#88 with the
recent kmod update an issue with our signed packages was uncovered:

On Wed, Jan 08, 2020 at 01:45:21PM +0100, Salvatore Bonaccorso wrote:
> Hi Benjamin,
> 
> On Wed, Jan 08, 2020 at 01:07:20PM +0100, Salvatore Bonaccorso wrote:
> > Hi Benjamin,
> > 
> > On Wed, Jan 08, 2020 at 09:24:30AM +0900, Benjamin Poirier wrote:
> > [...]
> > > Looks like the modules are built before lttng-sessiond is started:
> > > 	Setting up lttng-modules-dkms (2.11.0-2) ...
> > > 	Loading new lttng-modules-2.11.0 DKMS files...
> > > 	Building for 5.4.0-2-amd64
> > > 	Building initial module for 5.4.0-2-amd64
> > > 	Done.
> > > 
> > > 	lttng-lib-ring-buffer.ko:
> > > 	Running module version sanity check.
> > > 	 - Original module
> > > 	   - No original module exists within this kernel
> > > 	 - Installation
> > > 	   - Installing to /lib/modules/5.4.0-2-amd64/updates/dkms/
> > > 
> > > 	[...]
> > > 
> > > 	depmod...
> > > 
> > > 	DKMS: install completed.
> > > 	Setting up linux-headers-5.4.0-2-amd64 (5.4.8-1) ...
> > > 	/etc/kernel/header_postinst.d/dkms:
> > > 	dkms: running auto installation service for kernel 5.4.0-2-amd64:.
> > > 	Setting up sudo (1.8.29-1) ...
> > > 	Setting up babeltrace (1.5.7-2) ...
> > > 	Setting up liburcu6:amd64 (0.11.1-2) ...
> > > 	Setting up linux-headers-amd64 (5.4.8-1) ...
> > > 	Setting up liblttng-ctl0:amd64 (2.11.0-3) ...
> > > 	Setting up lttng-tools (2.11.0-3) ...
> > > 
> > > Still, it doesn't work.
> > > 
> > > > Simply restarting the sessiond should fix this.
> > > 
> > > I tried restarting lttng-sessiond or rebooting the machine but it was no
> > > help, lttng-sessiond always reports:
> > > 	Error: Failed to load kmod library resources
> > > 	Warning: No kernel tracer available
> > > 
> > > A quick look into the code shows that is:
> > > src/bin/lttng-sessiond/modprobe.c
> > > 	kmod_set_log_fn(*ctx, log_kmod, NULL);
> > > 	ret = kmod_load_resources(*ctx);
> > > 	if (ret < 0) {
> > > 		ERR("Failed to load kmod library resources");
> > > 		goto error;
> > > 	}
> > > 
> > > I didn't dig into libkmod, but I noticed (using opensnoop.bt) the
> > > following:
> > > 	8071   lttng-sessiond      2   0 /lib/modules/5.4.0-2-amd64/modules.dep.bin
> > > 	8071   lttng-sessiond      2   0 /lib/modules/5.4.0-2-amd64/modules.alias.bin
> > > 	8071   lttng-sessiond      2   0 /lib/modules/5.4.0-2-amd64/modules.symbols.bin
> > > 	8071   lttng-sessiond      2   0 /lib/modules/5.4.0-2-amd64/modules.builtin.alias.bin
> > > 
> > > On another machine which I haven't yet updated and where lttng still
> > > works, I see:
> > > 	193519 lttng-sessiond      2   0 /lib/modules/5.4.0-1-amd64/modules.dep.bin
> > > 	193519 lttng-sessiond      2   0 /lib/modules/5.4.0-1-amd64/modules.alias.bin
> > > 	193519 lttng-sessiond      2   0 /lib/modules/5.4.0-1-amd64/modules.symbols.bin
> > > 	193519 lttng-sessiond      2   0 /lib/modules/5.4.0-1-amd64/modules.builtin.bin
> > > 
> > > Not sure if /lib/modules/5.4.0-2-amd64/modules.builtin.alias.bin is
> > > relevant but it's an empty file...
> > > 
> > > After downgrading libkmod2 from
> > > 	Version: 26+20191223-1
> > > to
> > > 	Version: 26-3
> > > the issue with lttng is no longer apparent:
> > > 	root@vsid:/tmp# lttng list --kernel
> > > 	Kernel events:
> > > 	-------------
> > > 	      asoc_snd_soc_bias_level_start (loglevel: TRACE_EMERG (0)) (type: tracepoint)
> > > 	      asoc_snd_soc_bias_level_done (loglevel: TRACE_EMERG (0)) (type: tracepoint)
> > > 	      asoc_snd_soc_dapm_start (loglevel: TRACE_EMERG (0)) (type: tracepoint)
> > > 	[...] 
> > > 
> > 
> > Should we track this in a separate bug from #948257?
> 
> So here is what I think is part of what is going on (unless there is
> something broken in my analysis):
> 
> Since 898490c010b5 ("moduleparam: Save information about built-in
> modules in separate file")[1] which is in 5.2-rc1, there is a new
> modules.builtin.modinfo provided.
> 
>  [1]: <https://git.kernel.org/linus/898490c010b5d2e499e03b7e815fc214209ac583>
> 
> This one is installed in the -unsigned binary packages but not copied
> over into the signing template, so the signed linux image packages do
> not contain it.
> 
> Now with kmod/26+20191223-1 we have 60084cf1cb24 ("libkmod: Add parser
> for modules.builtin.modinfo")[2] adding the parser and [3] and [4]
> using that.
> 
>  [2]: <https://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git/commit/?id=60084cf1cb24dc3a257976c0d539a4c3ffda5db5>
>  [3]: <https://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git/commit/?id=73eed2aba3cbe18bbda40f18f7bc32e8de1ec81f>
>  [4]: <https://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git/commit/?id=b866b2165ae6cf18fb26b635f4a7ee57c0334731>

Merge request:
https://salsa.debian.org/kernel-team/linux/merge_requests/201

Regards,
Salvatore

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web