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

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

Bug#884094: register_key_type symbol missing, ABI counter not incremented

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

Contents

  Bug#884094: register_key_type symbol missing, ABI counter not incremented Sergio Gelato <Sergio.Gelato@astro.su.se> - 2017-12-11 12:00 +0100
    Bug#884094: register_key_type symbol missing, ABI counter not incremented Ben Hutchings <ben@decadent.org.uk> - 2017-12-11 17:10 +0100
      Bug#884094: register_key_type symbol missing, ABI counter not incremented Sergio Gelato <Sergio.Gelato@astro.su.se> - 2017-12-12 08:40 +0100
        Bug#884094: register_key_type symbol missing, ABI counter not incremented Ben Hutchings <ben@decadent.org.uk> - 2017-12-12 17:00 +0100
        Bug#884094: register_key_type symbol missing, ABI counter not incremented Liam Healy <lnp@healy.washington.dc.us> - 2017-12-13 15:40 +0100
    Bug#884094: User message Liam Healy <lnp@healy.washington.dc.us> - 2017-12-11 18:40 +0100
    Bug#884094: Impact on NFS shared Louis Chanouha <louis.chanouha@univ-toulouse.fr> - 2017-12-15 17:30 +0100
      Bug#884094: Impact on NFS shared Ben Hutchings <ben@decadent.org.uk> - 2017-12-15 19:10 +0100
        Bug#884094: Impact on NFS shared Louis Chanouha <louis.chanouha@univ-toulouse.fr> - 2017-12-16 00:40 +0100
          Bug#884094: Impact on NFS shared Ben Hutchings <ben@decadent.org.uk> - 2017-12-16 03:30 +0100
            Bug#884094: Impact on NFS shared Louis Chanouha <louis.chanouha@univ-toulouse.fr> - 2017-12-18 13:30 +0100
              Bug#884094: Impact on NFS shared Ben Hutchings <ben@decadent.org.uk> - 2017-12-19 04:50 +0100
    Bug#884094: marked as done (register_key_type symbol missing, ABI  counter not incremented) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2018-02-22 17:10 +0100

#59604 — Bug#884094: register_key_type symbol missing, ABI counter not incremented

Package: linux-image-4.9.0-4-amd64
Version: 4.9.65-3
Severity: important
Affects: openafs-modules-dkms

debian/patches/debian/keys-limit-abi-change-in-4.9.59.patch renames
register_key_type to register_key_type_2 without bumping the ABI counter,
breaking OpenAFS kernel modules (package openafs-modules-dkms) built
against 4.9.51.

Symptom:
[   35.911739] openafs: Unknown symbol register_key_type (err 0)
and the module fails to load.

[toc] | [next] | [standalone]

#59612

[Multipart message — attachments visible in raw view] — view raw

On Mon, 2017-12-11 at 11:48 +0100, Sergio Gelato wrote:
> Package: linux-image-4.9.0-4-amd64
> Version: 4.9.65-3
> Severity: important
> Affects: openafs-modules-dkms
> 
> debian/patches/debian/keys-limit-abi-change-in-4.9.59.patch renames
> register_key_type to register_key_type_2 without bumping the ABI counter,
> breaking OpenAFS kernel modules (package openafs-modules-dkms) built
> against 4.9.51.
> 
> Symptom:
> [   35.911739] openafs: Unknown symbol register_key_type (err 0)
> and the module fails to load.

Sorry, I didn't realise this was used by out-of-tree modules (I do
usually check).  I don't think there's any good way to deal with this
now, other than to force a rebuild of the module.

Ben.

-- 
Ben Hutchings
A free society is one where it is safe to be unpopular. - Adlai
Stevenson

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

#59627

* Ben Hutchings [2017-12-11 15:59:38 +0000]:
> I don't think there's any good way to deal with this
> now, other than to force a rebuild of the module.

Was afraid of that. It's what I did, of course, but it complicates the rollout.
(I ran "dkms remove openafs/1.6.20 -k $(uname -r); dkms install openafs/1.6.20".)

Will there be a jessie backport of that kernel, to replace 4.9.51-1~bpo8+1 ?

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

#59635

[Multipart message — attachments visible in raw view] — view raw

On Tue, 2017-12-12 at 08:25 +0100, Sergio Gelato wrote:
> * Ben Hutchings [2017-12-11 15:59:38 +0000]:
> > I don't think there's any good way to deal with this
> > now, other than to force a rebuild of the module.
> 
> Was afraid of that. It's what I did, of course, but it complicates the rollout.
> (I ran "dkms remove openafs/1.6.20 -k $(uname -r); dkms install openafs/1.6.20".)
> 
> Will there be a jessie backport of that kernel, to replace 4.9.51-1~bpo8+1 ?

Yes.  I already uploaded it but it's waiting for approval.

Ben.

-- 
Ben Hutchings
Unix is many things to many people,
but it's never been everything to anybody.

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

#59641

On Tue, Dec 12, 2017 at 2:25 AM, Sergio Gelato
<Sergio.Gelato@astro.su.se> wrote:
> * Ben Hutchings [2017-12-11 15:59:38 +0000]:
>> I don't think there's any good way to deal with this
>> now, other than to force a rebuild of the module.
>
> Was afraid of that. It's what I did, of course, but it complicates the rollout.
> (I ran "dkms remove openafs/1.6.20 -k $(uname -r); dkms install openafs/1.6.20".)

Thanks for posting the workaround instructions. For the benefit of
others, these are the complete set of commands that I used to restore
AFS access

sudo dkms remove openafs/1.6.20 -k $(uname -r); sudo dkms install openafs/1.6.20
sudo modprobe openafs
sudo systemctl stop openafs-client.service
sudo systemctl start openafs-client.service
aklog

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

#59615 — Bug#884094: User message

I have experienced this same problem suddenly on doing a safe-upgrade.
Thank you for identifying the cause and reporting the problem. For the
benefit of those users who will also encounter the problem and search
for the cause, the user experience symptom is that on aklog, the
following message is returned:

aklog: a pioctl failed while obtaining tokens for ....

If dmesg shows the message reported, then this is the cause.

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

#59672 — Bug#884094: Impact on NFS shared

[Multipart message — attachments visible in raw view] — view raw

Thie 4.9.0-4 update broke my NFS mounted sahred, with the following line 
in syslog:

dns_resolver: Unknown symbol register_key_type_2 (err 0)

Rollback to kernel 4.9.0-3-amd64 solves the issues, but i think this bug 
should be considered as critical.


Louis



-- 

*Logo UFTMiPLouis Chanouha | **Systèmes & Réseaux | Administrateur du SCOUT*
/Service Numérique de l'Université de Toulouse/
*Université Fédérale Toulouse Midi-Pyrénées*
15 rue des Lois - BP 61321 - 31013 Toulouse Cedex 6
Tél. : +33(0)5 61 10 80 45 <tel:+33561108045> / poste int. : 18045

louis.chanouha@univ-toulouse.fr
Facebook 
<http://www.facebook.com/pages/Universit%C3%A9-de-Toulouse/189718587732582> | 
Twitter <https://twitter.com/#%21/Univ_Toulouse> | www.univ-toulouse.fr 
<http://www.univ-toulouse.fr/>

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

#59673 — Bug#884094: Impact on NFS shared

[Multipart message — attachments visible in raw view] — view raw

On Fri, 2017-12-15 at 17:08 +0100, Louis Chanouha wrote:
> Thie 4.9.0-4 update broke my NFS mounted sahred, with the following line 
> in syslog:
> 
> dns_resolver: Unknown symbol register_key_type_2 (err 0)
> 
> Rollback to kernel 4.9.0-3-amd64 solves the issues, but i think this bug 
> should be considered as critical.

This means you are running the old kernel with new modules.  Either you
have not rebooted or your boot loader is misconfigured.

Ben

-- 
Ben Hutchings
Teamwork is essential - it allows you to blame someone else.

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

#59677 — Bug#884094: Impact on NFS shared

I'm not Linux kernel neither Debian boot friendly, my apologies if I'm missing anything. 
This error occurred after a reboot on an fresh install of Debian STRETCH (not upgraded from Jessie), consecutive after an apt upgrade command (with kernel update). 
This installation is very standard (but with LVM layer), no modifications regarding boot configuration were done (debian installer did the job). 

Tell me if you need something from me, I would me glad to help. 

Regards, 
Louis 
> ----------------------------------------
> From: Ben Hutchings <ben@decadent.org.uk>
> Sent: Fri Dec 15 19:05:30 CET 2017
> To: Louis Chanouha <louis.chanouha@univ-toulouse.fr>, <884094@bugs.debian.org>
> Subject: Re: Bug#884094: Impact on NFS shared
> 
> 
> On Fri, 2017-12-15 at 17:08 +0100, Louis Chanouha wrote:
> > Thie 4.9.0-4 update broke my NFS mounted sahred, with the following line 
> > in syslog:
> > 
> > dns_resolver: Unknown symbol register_key_type_2 (err 0)
> > 
> > Rollback to kernel 4.9.0-3-amd64 solves the issues, but i think this bug 
> > should be considered as critical.
> 
> This means you are running the old kernel with new modules.  Either you
> have not rebooted or your boot loader is misconfigured.
> 
> Ben
> 
> -- 
> Ben Hutchings
> Teamwork is essential - it allows you to blame someone else.
> 

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

#59680 — Bug#884094: Impact on NFS shared

[Multipart message — attachments visible in raw view] — view raw

On Sat, 2017-12-16 at 00:28 +0100, Louis Chanouha wrote:
> I'm not Linux kernel neither Debian boot friendly, my apologies if
> I'm missing anything. 
> This error occurred after a reboot on an fresh install of Debian
> STRETCH (not upgraded from Jessie), consecutive after an apt upgrade
> command (with kernel update). 
> This installation is very standard (but with LVM layer), no
> modifications regarding boot configuration were done (debian
> installer did the job). 
> 
> Tell me if you need something from me, I would me glad to help.

Try these commands:

uname -v
dpkg -l linux-image-4.9.0-4-amd64
debsums -c linux-image-4.9.0-4-amd64

Ben.

-- 
Ben Hutchings
Teamwork is essential - it allows you to blame someone else.

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

#59703 — Bug#884094: Impact on NFS shared

Here are the results:

root@xxx:~# uname -v
#1 SMP Debian 4.9.51-1 (2017-09-28)
root@xxx:~# dpkg -l linux-image-4.9.0-4-amd64
ii  linux-image-4.9.0-4-amd64                            4.9.65-3                        amd64                           Linux 4.9 for 64-bit PCs
root@video-test:~# debsums -c linux-image-4.9.0-4-amd64
/boot/System.map-4.9.0-4-amd64
/boot/config-4.9.0-4-amd64
/boot/vmlinuz-4.9.0-4-amd64
root@xxx:~# uname -a
Linux xxx 4.9.0-4-amd64 #1 SMP Debian 4.9.51-1 (2017-09-28) x86_64 GNU/Linux

Still available for further informations. 

> ----------------------------------------
> From: Ben Hutchings <ben@decadent.org.uk>
> Sent: Sat Dec 16 03:16:31 CET 2017
> To: Louis Chanouha <louis.chanouha@univ-toulouse.fr>, <884094@bugs.debian.org>
> Subject: Re: Bug#884094: Impact on NFS shared
> 
> 
> On Sat, 2017-12-16 at 00:28 +0100, Louis Chanouha wrote:
> > I'm not Linux kernel neither Debian boot friendly, my apologies if
> > I'm missing anything. 
> > This error occurred after a reboot on an fresh install of Debian
> > STRETCH (not upgraded from Jessie), consecutive after an apt upgrade
> > command (with kernel update). 
> > This installation is very standard (but with LVM layer), no
> > modifications regarding boot configuration were done (debian
> > installer did the job). 
> > 
> > Tell me if you need something from me, I would me glad to help.
> 
> Try these commands:
> 
> uname -v
> dpkg -l linux-image-4.9.0-4-amd64
> debsums -c linux-image-4.9.0-4-amd64
> 
> Ben.
> 
> -- 
> Ben Hutchings
> Teamwork is essential - it allows you to blame someone else.
> 

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

#59707 — Bug#884094: Impact on NFS shared

[Multipart message — attachments visible in raw view] — view raw

On Mon, 2017-12-18 at 13:18 +0100, Louis Chanouha wrote:
> Here are the results:
> 
> root@xxx:~# uname -v
> #1 SMP Debian 4.9.51-1 (2017-09-28)

So you are running the old kernel version...

> root@xxx:~# dpkg -l linux-image-4.9.0-4-amd64
> ii  linux-image-4.9.0-4-amd64                            4.9.65-3                        amd64                           Linux 4.9 for 64-bit PCs

...and the new kernel and modules are installed...

> root@video-test:~# debsums -c linux-image-4.9.0-4-amd64
> /boot/System.map-4.9.0-4-amd64
> /boot/config-4.9.0-4-amd64
> /boot/vmlinuz-4.9.0-4-amd64
[...]

...but /boot doesn't match what was in the package.

So you still have files from the old package in /boot.  Perhaps you
changed which device is used as /boot at some point.

Anyway, if the kernel isn't properly installed that's not a kernel bug.

Ben.

-- 
Ben Hutchings
73.46% of all statistics are made up.

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

#60302 — Bug#884094: marked as done (register_key_type symbol missing, ABI counter not incremented)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Thu, 22 Feb 2018 16:56:46 +0100
with message-id <1519315006.2617.231.camel@decadent.org.uk>
and subject line Re: register_key_type symbol missing, ABI counter not incremented
has caused the Debian Bug report #884094,
regarding register_key_type symbol missing, ABI counter not incremented
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
884094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884094
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

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

csiph-web