[Bug 1625319] Re: [LTCTest] SR-IOV VF hotplug failing: cannot limit locked memory of process
As per comment #5, marking as "Fix Released". ** Changed in: apparmor (Ubuntu) Status: Incomplete => Fix Released ** Changed in: apparmor (Ubuntu) Assignee: Taco Screen team (taco-screen-team) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1625319 Title: [LTCTest] SR-IOV VF hotplug failing: cannot limit locked memory of process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1625319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1625319] Re: [LTCTest] SR-IOV VF hotplug failing: cannot limit locked memory of process
As Seth mentioned, this unofficial kernel may be missing some AppArmor fixes that are included in the official Ubuntu kernels. Can you please try 4.8.0-11.12 from yakkety-proposed and let us know if this bug is still present? https://launchpad.net/ubuntu/+source/linux/4.8.0-11.12 Thanks! ** Changed in: apparmor (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1625319 Title: [LTCTest] SR-IOV VF hotplug failing: cannot limit locked memory of process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1625319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1625319] Re: [LTCTest] SR-IOV VF hotplug failing: cannot limit locked memory of process
Shivaprasad reported this last week in the #apparmor irc channel. What I think we figured out at the time: - The 4.7.0-based kernel may or may not be missing fixes from Ubuntu kernels - 9663676416 is suspiciously larger than 32 bit integer - the profile didn't mention rlimits, so they should not have been 'enforced' I had a wild-guess that "set rlimit memlock 1," might provide useful debugging information. John thought otherwise. John asked for the security/apparmor/rlim_names.h file that's created during the build. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1625319 Title: [LTCTest] SR-IOV VF hotplug failing: cannot limit locked memory of process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1625319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
