[Bug 1096497] Re: Disabling lock debugging due to kernel taint with no apparent cause
Well, the question is, is it still there; on Saucy (3.11.0-4-generic #9): # grep -i taint /var/log/kern.log Aug 26 11:34:52 major vmunix: [0.903410] crc_itu_t: module verification failed: signature and/or required key missing - tainting kernel Aug 27 11:55:01 major vmunix: [0.903210] crc_itu_t: module verification failed: signature and/or required key missing - tainting kernel Aug 28 11:44:37 major vmunix: [0.903483] crc_itu_t: module verification failed: signature and/or required key missing - tainting kernel Aug 29 11:47:56 major vmunix: [0.903025] crc_itu_t: module verification failed: signature and/or required key missing - tainting kernel that does look like the first module loaded; so we're still getting the taint - at least it does give a clue to what's going on now. ** Changed in: linux (Ubuntu) Status: Expired = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096497 Title: Disabling lock debugging due to kernel taint with no apparent cause To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1096497] Re: Disabling lock debugging due to kernel taint with no apparent cause
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096497 Title: Disabling lock debugging due to kernel taint with no apparent cause To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1096497] Re: Disabling lock debugging due to kernel taint with no apparent cause
Will someone please stop this robot closing the bug - it's still there! Ignoring problems doesn't make them go away. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096497 Title: Disabling lock debugging due to kernel taint with no apparent cause To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1096497] Re: Disabling lock debugging due to kernel taint with no apparent cause
Hmm so I'm still seeing a taint on 3.9.0-7-generic #15-Ubuntu on Saucy; it seems to be being triggered by the crc_itu_t module for no apparent reason: [0.865613] crc_itu_t: module verification failed: signature and/or required key missing - tmeainting kernel Is this the same bug or more specific? ** Changed in: linux (Ubuntu) Status: Expired = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096497 Title: Disabling lock debugging due to kernel taint with no apparent cause To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1096497] Re: Disabling lock debugging due to kernel taint with no apparent cause
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096497 Title: Disabling lock debugging due to kernel taint with no apparent cause To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1096497] Re: Disabling lock debugging due to kernel taint with no apparent cause
@Joseph - sorry for the delay, been moving house! I don't think 64748a2c9062da0c32b59c1b368a86fc4613b1e1 was being sent to stable, it doesn't fix anything as it just gives you more info about it being tainted. The real fix will have to be in make-kpkg to stop it altering modules after signing (bug #1099371). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096497 Title: Disabling lock debugging due to kernel taint with no apparent cause To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1096497] Re: Disabling lock debugging due to kernel taint with no apparent cause
@Chris, do you know if commit 64748a2c9062da0c32b59c1b368a86fc4613b1e1 will be sent to stable as well? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096497 Title: Disabling lock debugging due to kernel taint with no apparent cause To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1096497] Re: Disabling lock debugging due to kernel taint with no apparent cause
Hi there, Thanks for finding my patch on LKML, two points: 1) The updated reporting has been incorporated upstream for 3.9 by Rusty in commit 64748a2c9062da0c32b59c1b368a86fc4613b1e1. 2) Rusty additionally changed the code so that loading an unsigned module no longer disables lockdep checking in commit 373d4d099761cb1f637bed488ab3871945882273. The cause of the issue is that *after* doing the module install make- kpkg runs objcopy on the modules to copy out the debug sections for a debug package and then uses objcopy to remove the same debug sections (along with the crypto signatures) from the ones in the main package. :-(I've reported that as Ubuntu bug #1099371 (though my initial diagnosis was incorrect, I've updated it in the comments and will correct the description now). So until that's fixed all Raring kernels will be tainted on boot due to loading unsigned kernel modules (unless Ubuntu disables CONFIG_MODULE_SIG). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096497 Title: Disabling lock debugging due to kernel taint with no apparent cause To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1096497] Re: Disabling lock debugging due to kernel taint with no apparent cause
** Changed in: linux (Ubuntu) Assignee: Joseph Salisbury (jsalisbury) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096497 Title: Disabling lock debugging due to kernel taint with no apparent cause To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1096497] Re: Disabling lock debugging due to kernel taint with no apparent cause
It seems the proper fix is still being discussed upstream: https://lkml.org/lkml/2013/1/12/19 I'll await a final version of the patch then build a test kernel. ** Changed in: linux (Ubuntu) Status: In Progress = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096497 Title: Disabling lock debugging due to kernel taint with no apparent cause To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1096497] Re: Disabling lock debugging due to kernel taint with no apparent cause
Thanks for finding that, Dave. Saves allot of time bisecting. I can build a test kernel with that patch applied. I'll post a link to the kernel here and test it myself as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096497 Title: Disabling lock debugging due to kernel taint with no apparent cause To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1096497] Re: Disabling lock debugging due to kernel taint with no apparent cause
Joseph: It looks like it is the mod sign stuff; see this lkml thread: https://lkml.org/lkml/2013/1/11/132 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096497 Title: Disabling lock debugging due to kernel taint with no apparent cause To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1096497] Re: Disabling lock debugging due to kernel taint with no apparent cause
** Changed in: linux (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096497 Title: Disabling lock debugging due to kernel taint with no apparent cause To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1096497] Re: Disabling lock debugging due to kernel taint with no apparent cause
** Changed in: linux (Ubuntu) Assignee: (unassigned) = Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096497 Title: Disabling lock debugging due to kernel taint with no apparent cause To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1096497] Re: Disabling lock debugging due to kernel taint with no apparent cause
I can reproduce this issue with Raring. It doesn't seem to happen with Quantal. The value of 2 for /proc/sys/kernel/tainted may indicate: #define TAINT_UNSAFE_SMP2 Since I can reproduce the bug, I'll perform a kernel bisect to see what commit introduced this regression. ** Tags added: regression-release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096497 Title: Disabling lock debugging due to kernel taint with no apparent cause To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1096497] Re: Disabling lock debugging due to kernel taint with no apparent cause
* Joseph Salisbury (joseph.salisb...@canonical.com) wrote: I can reproduce this issue with Raring. It doesn't seem to happen with Quantal. The value of 2 for /proc/sys/kernel/tainted may indicate: #define TAINT_UNSAFE_SMP2 Be careful - I think that's a value that's shifted; my reading of it was that it's actually the TAINT_FORCED (sorry can't remember exact name) that has a value of 1, and 11 is 2. Since I can reproduce the bug, I'll perform a kernel bisect to see what commit introduced this regression. ** Tags added: regression-release Dave -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096497 Title: Disabling lock debugging due to kernel taint with no apparent cause To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
