RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 851013 - start lxc crash the kernel
Summary: start lxc crash the kernel
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.3
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Aristeu Rozanski
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-23 05:57 UTC by Steve Kieu
Modified: 2013-02-05 19:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-05 19:08:41 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Steve Kieu 2012-08-23 05:57:08 UTC 
Description of problem:

Security context inside CT is not tight, process inside guest can crash the host.
Also when start lxc - mount the sysfs affect the host as well - so sysfs is not correctly support multiple namespace.

Version-Release number of selected component (if applicable):


How reproducible:

I have a container and in the start up scripts it runs some command that interact with hardware (not quite sure what though as the cleanup and tune of the LXC is not perfect). Nevertheless the lxc config file does not allow to access to these devices and the sysfs inside the CT is read only - it still be able to crashed the kernel. After starting for a while I got:

* The host /sys is mounted readonly
* Then crashed:
Firmware bug the BIOS has corrupted hw-PMU resources MSR 186 is 53003c 

>> and a lot of dumping module ...

The CT fstab looks like this

none /opt/lxc/guest/cacti/dev/pts    devpts newinstance,ptmxmode=0666 0 0
none /opt/lxc/guest/cacti/proc    proc    nodev,noexec,nosuid 0 0
none /opt/lxc/guest/cacti/sys    sysfs    defaults,ro 0 0
none /opt/lxc/guest/cacti/dev/shm tmpfs defaults 0 0

and after started my host sysfs mounted at /sys has became readonly

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:

These above problem has not happened with kernel 3.2.18 and above. I think these fixes has gone into mainline, please do port it to RHEL kernel.


Additional info:
Comment 2 Aristeu Rozanski 2012-09-25 14:01:02 UTC 
The hardware message suggests bug on the BIOS/hardware, not in the kernel. Can you reproduce the problem in another machine (different brand/model if possible)
Comment 3 Steve Kieu 2012-09-25 22:58:05 UTC 
I am fore sure these bug:

* if mount sysfs for the guest as readonly, the host sysfs (current one) will be readonly too. The same apply for readwrite. 

That prevents me to use lxc at all. I need it to be mounted on the guest readonly because I do nto want any one on the guest (root) to be able to write into it to chnage the host settings.

And the crash here is probably due to kernel - hardware combination. But it does not happen with the same kernel - hardware if I do not use LXC at all.

Anyway currently the reported system is in production now, and we use custom built kernel 3.2.28 which is stable. There is no choice for me to test it again on that hardware. The lxc mount sysfs bug can be repeated in any system, even on a kvm host - and not only with readhat kernel but also with vanila 2.6.32.XX kernel. I have not test the procfs when in use with lxc, not sure how well support lxc is with 2.6.32.xx though.

If readhat can backported these lxc fixes from newer kernel to redhat 2.6.32.xx kernel then I do not need to use custom kernel which will be great.

Thanks
Comment 4 Steve Kieu 2012-09-25 23:00:32 UTC 
A hint for backporting is that vanilla  kernel 2.6.35.13 on ward does not have the sysfs or any other lxc related problem
Comment 5 Aristeu Rozanski 2012-09-26 13:29:10 UTC 
Do you still have a full dmesg out of the crash? I'll need a sosreport from the
machine too.
Comment 6 RHEL Program Management 2012-12-14 08:51:28 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 7 Aristeu Rozanski 2013-01-08 16:50:16 UTC 
Steve?
Comment 8 Aristeu Rozanski 2013-02-05 19:08:41 UTC 
I'm closing this bug with INSUFICIENT_DATA. Feel free to reopen when the requested
information is available.
Note You need to log in before you can comment on or make changes to this bug.