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 844421 - /dev/pts must always use the 'newinstance' mount flag to correctly support LXC
Summary: /dev/pts must always use the 'newinstance' mount flag to correctly support LXC
Keywords:
Status: CLOSED DUPLICATE of bug 527483
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Libvirt Maintainers
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-30 14:34 UTC by Giuseppe Ragusa
Modified: 2012-09-26 10:36 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-25 09:42:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Giuseppe Ragusa 2012-07-30 14:34:27 UTC 
Description of problem:
See Bugzilla #501718

I further note that to always correctly mount devpts as newinstance, maybe changes should be made to dracut (initial mount inside initramfs) and initscripts (rc.sysinit) packages too.

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


How reproducible:


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


Expected results:


Additional info:
Comment 3 Daniel Berrangé 2012-09-25 09:42:49 UTC 
I don't know why this bug was opened against libvirt, because host OS setup is not within libvirt's realm of responsibility. This is either the kernel or base OS' job to fix.
Comment 4 Daniel Berrangé 2012-09-25 09:48:01 UTC 
FYI see the kernel bug 527483
Comment 5 Giuseppe Ragusa 2012-09-26 10:01:45 UTC 
There's no public access to bug 527483 so please summarize your point here.

As for the libvirt affair, I actually opened this bug against kernel (after looking at discussion in bug 501718) and also noted that maybe changes were due in dracut and initscripts too.

Component was recently changed to libvirt by lwang

I supposed that changing kernel defaults could have (potentially) far reaching consequences (maybe inappropriate in RHEL), so I did not immediately reacted when component was switched to libvirt, since I understood it as an assumption that changing the devpts setup code in the LXC driver could be enough (maybe coupled with the aformementioned dracut/initscripts changes).
Comment 6 Daniel Berrangé 2012-09-26 10:09:09 UTC 
Sorry, I didn't notice that the kernel bug was private - it should not have been, so I made it public now. Libvirt already does the only thing I can do, which is to use 'newinstance' when creating the containers. The rest has to be done by the kernel or low level OS setup tools
Comment 7 Giuseppe Ragusa 2012-09-26 10:26:01 UTC 
Thank you very much for your help/clarification.

I didn't read the libvirt code on this issue, so thank for clarifying this too.

Should I change this back to kernel (and reopen it) or should I open another one (hoping it does not get changed comnponent again)?

What do you think about the feasibility of such a kernel policy change in RHEL (the kernel reasoning in bug 501718 was for Fedora) vs. the multiple components approach (opening multiple bugs: for dracut and initscripts, since libvirt is already ok)?
Comment 8 Daniel Berrangé 2012-09-26 10:30:50 UTC 
No need to do anything with this bug, since we already have another one open against RHEL kernel to track it.

To be honest, I think the liklihood of this being fixed in the kernel in RHEL-6 lifetime is fairly low, because LXC in general is still lacking so many security related features, that this is low impact in the great scheme of things. In addition there is a quick workaround for people who do actually care - just edit /etc/fstab on their host to add the 'newinstance' flag against the /dev/pts entry and reboot.
Comment 9 Daniel Berrangé 2012-09-26 10:36:30 UTC 

*** This bug has been marked as a duplicate of bug 527483 ***
Note You need to log in before you can comment on or make changes to this bug.