[Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

[vinod]

This package update is still braking few instances hosted on AWS. it is
the same issue what we have seen in version "libjson-c2 0.11-4ubuntu2.1"
and impacted a lot of users.

same issue we are facing in the version libjson-c2/now 0.11-4ubuntu2.6
which caused few aws instances to go in kernel panic mode.


do ubuntu have through testing before pushing update and what about revert back. can ubuntu revert back to previous package if unattended upgrade sees any error?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to json-c in Ubuntu.
https://bugs.launchpad.net/bugs/1878723

Title:
  Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

Status in json-c package in Ubuntu:
  Triaged

Bug description:
  Installing the 0.11-4ubuntu2.1 security update on a Xenial system with
  upstart installed, the system crashes with a kernel panic.

  The error message is:

  [   99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
  [   99.992278] 
  [   99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu
  [   99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
  [   99.996057]  0000000000000086 0f10ff6977efbf32 ffff88003d45fe10 ffffffff8140926b
  [   99.996057]  ffffffff81caddf8 ffff88003d45fea8 ffff88003d45fe98 ffffffff81195a84
  [   99.996057]  ffff880000000010 ffff88003d45fea8 ffff88003d45fe40 0f10ff6977efbf32
  [   99.996057] Call Trace:
  [   99.996057]  [<ffffffff8140926b>] dump_stack+0x6d/0x92
  [   99.996057]  [<ffffffff81195a84>] panic+0xd3/0x227
  [   99.996057]  [<ffffffff81088ded>] do_exit+0xb9d/0xba0
  [   99.996057]  [<ffffffff81088e77>] do_group_exit+0x47/0xb0
  [   99.996057]  [<ffffffff81088ef4>] SyS_exit_group+0x14/0x20
  [   99.996057]  [<ffffffff818449db>] entry_SYSCALL_64_fastpath+0x22/0xcb
  [   99.996057] Kernel Offset: disabled

  Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue.

  Steps to reproduce:
  * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d)
  * Install upstart: apt-get install upstart-sysv
  * Reboot
  * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic.
  * To repeat the kernel panic, run dpkg --configure -a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions