Ubuntu
linux package

SECCOMP causes kernel panic on EC2 AMD64 image

Bug #725089 reported by C de-Avillez
262
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
High
John Johansen

Bug Description

Release of Ubuntu: maverick
Package Version: linux-image-2.6.35-27-virtual 2.6.35-27.48
Expected Results: recoverable errors at most
Actual Results: kernel panic

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-27-virtual 2.6.35-27.48
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-27.48-virtual 2.6.35.11
Uname: Linux 2.6.35-27-virtual x86_64
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
Date: Fri Feb 25 16:17:47 2011
Ec2AMI: ami-4e29da27
Ec2AMIManifest: ubuntu-images-testing-us/ubuntu-maverick-daily-amd64-server-20110223.manifest.xml
Ec2AvailabilityZone: us-east-1d
Ec2InstanceType: m1.large
Ec2Kernel: aki-427d952b
Ec2Ramdisk: unavailable
Lspci:

Lsusb: Error: command ['lsusb'] failed with exit code 1:
ProcCmdLine: root=LABEL=uec-rootfs ro console=hvc0
ProcEnviron:
 LC_TIME=en_DK.utf8
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcModules: acpiphp 18752 0 - Live 0xffffffffa0000000
SourcePackage: linux

Revision history for this message
C de-Avillez (hggdh2) wrote :
Revision history for this message
C de-Avillez (hggdh2) wrote :

This is the output of ec2-get-console-output, after a reboot.

Revision history for this message
C de-Avillez (hggdh2) wrote :

Setting importance to High -- SRu testing failed

Changed in linux (Ubuntu):
importance: Undecided → High
Revision history for this message
C de-Avillez (hggdh2) wrote :

Also, please see https://wiki.ubuntu.com/QATeam/KernelSRU-maverick-2.6.35-27.48

John Johansen (jjohansen)
Changed in linux (Ubuntu):
assignee: nobody → John Johansen (jjohansen)
Revision history for this message
Stefan Bader (smb) wrote :

How many times was a reboot into the latest kernel tried? I ran some tests today and apart from one odd failure to boot a daily Maverick instance which went directly from pending into terminated, I was able to update and bring up two m1.large instance with 2.6.35-27.48-virtual.

(Note on the side that reboot and possibly halt from within the instance seem to be generally broken in Maverick. I noted this today when playing around with my local system. For Lucid "xm shutdown" will completely halt the instance, but for Maverick images I need to call "xm destroy" as well. Same with "xm reboot" and "xm reset")

So maybe we are just facing a rare failure case which needs investigation. But I would say it is not a regression.

Revision history for this message
John Johansen (jjohansen) wrote :

So after several tests I have replicated this on a 2.6.35-25-virtual kernel, not the crash is sporadic and does not show up every time.

So the bug is not a regression in the proposed linux-image-2.6.35-27-virtual 2.6.35-27.48 kernel.

Revision history for this message
Kees Cook (kees) wrote :

I've marked this test as a "skip" for -ec2 kernels until this bug is fixed.

summary: - QRT test-kernel-security causes kernel panic on EC2 AMD64 image
+ SECCOMP causes kernel panic on EC2 AMD64 image
Kees Cook (kees)
Changed in linux (Ubuntu):
status: New → Confirmed
security vulnerability: no → yes
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public Security information  
Everyone can see this security related information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.