[Bug 1636847] Re: unexpectedly large memory usage of mounted snaps
Is it possible (pun intended) to compromise on `CONFIG_SQUASHFS_DECOMP_MULTI` (which uses num_online_cpus) instead of `CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU` (which uses `num_possible_cpus`)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1636847 Title: unexpectedly large memory usage of mounted snaps To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1636847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1636847] Re: unexpectedly large memory usage of mounted snaps
The log message[1] says that this issues is under investigation: > For the moment turn it off while it can be investigated. Did we find the root cause? Seems like Debian is successfully uses it nowadays: ``` tar -xOzf linux_5.10.19-1.debian.tar.xz ./debian/config/config | fgrep CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU=y ``` [1] https://lists.ubuntu.com/archives/kernel- team/2016-October/080596.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1636847 Title: unexpectedly large memory usage of mounted snaps To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1636847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1708604] Re: Backport recent bbr bugfixes to 4.10 kernel
Sadly, we've already workedaround that problem with a custom-built module. Let me see if my colleagues can test the kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1708604 Title: Backport recent bbr bugfixes to 4.10 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1708604] Re: Backport recent bbr bugfixes to 4.10 kernel
** Description changed:
- 4.10 kernel is commonly used for test BBR Congestion Control
- deployments.
+ 4.10 kernel is commonly used to test BBR Congestion Control deployments.
- Recent 4.13 release had a bunch of fixes for the initial BBR release, namely:
+ Recent net-next pull in 4.13-rc1 had a bunch of fixes for the initial BBR
release, namely:
4aea287e90dd61a48268ff2994b56f9799441b62 tcp_bbr: cut pacing rate only if
filled pipe
f19fd62dafaf1ed6cf615dba655b82fa9df59074 tcp_bbr: introduce
bbr_bw_to_pacing_rate() helper
79135b89b8af304456bd67916b80116ddf03d7b6 tcp_bbr: introduce
bbr_init_pacing_rate_from_rtt() helper
1d3648eb5d1fe9ed3d095ed8fa19ad11ca4c8bc0 tcp_bbr: remove sk_pacing_rate=0
transient during init
32984565574da7ed3afa10647bb4020d7a9e6c93 tcp_bbr: init pacing rate on first
RTT sample
All of them marked as 'Fixes: 0f8782ea1497 ("tcp_bbr: add BBR congestion
control")', which makes them legitimate bugfixes.
All of them constrained to `net/ipv4/tcp_bbr.c` and should be trivial to
cherrypick into 4.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1708604
Title:
Backport recent bbr bugfixes to 4.10 kernel
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708604/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1708604] Re: Backport recent bbr bugfixes to 4.10 kernel
** Changed in: linux (Ubuntu) Status: Incomplete => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1708604 Title: Backport recent bbr bugfixes to 4.10 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1708604] [NEW] Backport recent bbr bugfixes to 4.10 kernel
Public bug reported:
4.10 kernel is commonly used for test BBR Congestion Control
deployments.
Recent 4.13 release had a bunch of fixes for the initial BBR release, namely:
4aea287e90dd61a48268ff2994b56f9799441b62 tcp_bbr: cut pacing rate only if
filled pipe
f19fd62dafaf1ed6cf615dba655b82fa9df59074 tcp_bbr: introduce
bbr_bw_to_pacing_rate() helper
79135b89b8af304456bd67916b80116ddf03d7b6 tcp_bbr: introduce
bbr_init_pacing_rate_from_rtt() helper
1d3648eb5d1fe9ed3d095ed8fa19ad11ca4c8bc0 tcp_bbr: remove sk_pacing_rate=0
transient during init
32984565574da7ed3afa10647bb4020d7a9e6c93 tcp_bbr: init pacing rate on first RTT
sample
All of them marked as 'Fixes: 0f8782ea1497 ("tcp_bbr: add BBR congestion
control")', which makes them legitimate bugfixes.
All of them constrained to `net/ipv4/tcp_bbr.c` and should be trivial to
cherrypick into 4.10.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1708604
Title:
Backport recent bbr bugfixes to 4.10 kernel
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708604/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 811016] Re: Move to /run breaks pbuilder --execute
Backport to Lucid? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/811016 Title: Move to /run breaks pbuilder --execute To manage notifications about this bug go to: https://bugs.launchpad.net/pbuilder/+bug/811016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 493156] Re: Please enable CONFIG_TASK_DELAY_ACCT
On Fri, May 4, 2012 at 5:20 AM, Balbir Singh wrote: > On Thu, May 3, 2012 at 11:59 PM, Christian Kujau > <493...@bugs.launchpad.net> wrote: >> Whooha, language! >> >> And I think they "fixed" it, albeit in a weird way: >> CONFIG_TASK_DELAY_ACCT is enabled in the kernel config, but the feature >> is still disabled unless the kernel is booted with "delayacct" as a boot >> parameter, see my comment above. >> > > I am not sure who made the decision and on what data, but > TASK_DELAY_ACCT should be the least of the problems when it comes to > overheads. > > The correct path IMHO is to show us the overhead and lets fix it if it > is unacceptable > Decision was totally right. One should NOT change behavior of kernel in the middle of LTS lifecycle (e.g. like it was done to CONFIG_NET_NS). Of cause it seems kinda strange that CONFIG_SCHEDSTATS is set to "y" and we are talking about CONFIG_TASK_DELAY_ACCT overhead. And yes, at least some numbers would be nice (esp. form Nicholas Janssen (xnicholas) who says that there is no overhead on his workload). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/493156 Title: Please enable CONFIG_TASK_DELAY_ACCT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iotop/+bug/493156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 804355] Re: jot random number generator broken in batch jobs
Oh... Previous patch by any means was not supposed to go to mainline. It was just dirty-hacky-PoC. Here is our QA version. Changes: * Switched to dpkg-source 3.0 (quilt) format * Added dbg package * Removed auto-generated files * Applied arc4random patch PS. I'm .rpm guy so I could messed up something there. PPS. Could it be also backported to Lucid? ** Patch added: "0001-rng-Use-arc4random-insted-of-time-based-random.patch" https://bugs.launchpad.net/ubuntu/+source/athena-jot/+bug/804355/+attachment/2882511/+files/0001-rng-Use-arc4random-insted-of-time-based-random.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/804355 Title: jot random number generator broken in batch jobs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/athena-jot/+bug/804355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 804355] Re: jot random number generator broken in batch jobs
Provided patch solving this issue. ** Patch added: "jot-9.0-random-number-geterator.patch" https://bugs.launchpad.net/ubuntu/+source/athena-jot/+bug/804355/+attachment/2875909/+files/jot-9.0-random-number-geterator.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/804355 Title: jot random number generator broken in batch jobs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/athena-jot/+bug/804355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 917643] Re: Adding IPv6 address to vlan in UNKNOWN state results in routes that expire within 30 days.
Tested on Ubuntu Oneiric's 3.0 - there is no such problem there. I've also can test it on other backport kernels when i get to work. ** Tags removed: needs-upstream-testing ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/917643 Title: Adding IPv6 address to vlan in UNKNOWN state results in routes that expire within 30 days. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/917643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 917643] Re: Adding IPv6 address to vlan in UNKNOWN state results in routes that expire within 30 days.
** Summary changed: - Adding address to vlan in UNKNOWN state results in routes that expire within 30 days. + Adding IPv6 address to vlan in UNKNOWN state results in routes that expire within 30 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/917643 Title: Adding IPv6 address to vlan in UNKNOWN state results in routes that expire within 30 days. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/917643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 917643] Re: Adding address to vlan in UNKNOWN state results in routes that expire within 30 days.
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/917643 Title: Adding address to vlan in UNKNOWN state results in routes that expire within 30 days. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/917643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 917643] [NEW] Adding address to vlan in UNKNOWN state results in routes that expire within 30 days.
Public bug reported: We noticed that after adding IPv6 address to vlan route to local network is added with expiration time. If after `ip link set vlanXXX up` up we wait until vlan's link state becomes UP then route get added without expiration time. We are using Ubuntu LTS 10.04: Ubuntu 2.6.32-32.62-server 2.6.32.38+drm33.16. To reproduce one can use following test script: $ cat test.sh ip addr del 2a02::1.1.1.1/64 dev vlan764 || : vconfig rem vlan764 || : vconfig set_name_type VLAN_PLUS_VID_NO_PAD vconfig add eth0 764 ip link set vlan764 up #sleep 5 ip addr add 2a02::1.1.1.1/64 dev vlan764 sleep 2 ip -6 route show $ sudo ./test.sh 2a02::/64 dev vlan764 proto kernel metric 256 expires 2591999sec mtu 8950 advmss 8890 hoplimit 4294967295 fe80::/64 dev eth0 proto kernel metric 256 mtu 8950 advmss 8890 hoplimit 4294967295 fe80::/64 dev vlan764 proto kernel metric 256 mtu 8950 advmss 8890 hoplimit 4294967295 default via fe80::226:bff:fe29:c40 dev vlan764 proto kernel metric 1024 expires 1799sec mtu 8950 advmss 8890 hoplimit 64 Notice `expires 2591999sec` in `2a02::/64 dev vlan764 ` route Now uncomment `#sleep 5` $ sudo ./test.sh 2a02::/64 dev vlan764 proto kernel metric 256 mtu 8950 advmss 8890 hoplimit 4294967295 fe80::/64 dev eth0 proto kernel metric 256 mtu 8950 advmss 8890 hoplimit 4294967295 fe80::/64 dev vlan764 proto kernel metric 256 mtu 8950 advmss 8890 hoplimit 4294967295 default via fe80::226:bff:fe29:c40 dev vlan764 proto kernel metric 1024 expires 0sec mtu 8950 advmss 8890 hoplimit 64 Now `expire` is gone. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: - We noticed that after we add IPv6 address to vlan route to local network - is added with expire date. If after `ip link set vlanXXX up` up we wait - until vlan's link state becomes UP then route get added without + We noticed that after adding IPv6 address to vlan route to local network + is added with expiration time. If after `ip link set vlanXXX up` up we + wait until vlan's link state becomes UP then route get added without expiration time. We are using Ubuntu LTS 10.04: Ubuntu 2.6.32-32.62-server 2.6.32.38+drm33.16. To reproduce one can use following test script: $ cat test.sh ip addr del 2a02::1.1.1.1/64 dev vlan764 || : vconfig rem vlan764 || : vconfig set_name_type VLAN_PLUS_VID_NO_PAD vconfig add eth0 764 ip link set vlan764 up #sleep 5 ip addr add 2a02::1.1.1.1/64 dev vlan764 sleep 2 ip -6 route show - $ sudo ./test.sh + $ sudo ./test.sh 2a02::/64 dev vlan764 proto kernel metric 256 expires 2591999sec mtu 8950 advmss 8890 hoplimit 4294967295 fe80::/64 dev eth0 proto kernel metric 256 mtu 8950 advmss 8890 hoplimit 4294967295 fe80::/64 dev vlan764 proto kernel metric 256 mtu 8950 advmss 8890 hoplimit 4294967295 default via fe80::226:bff:fe29:c40 dev vlan764 proto kernel metric 1024 expires 1799sec mtu 8950 advmss 8890 hoplimit 64 Notice `expires 2591999sec` in `2a02::/64 dev vlan764 ` route Now uncomment `#sleep 5` - $ sudo ./test.sh + $ sudo ./test.sh 2a02::/64 dev vlan764 proto kernel metric 256 mtu 8950 advmss 8890 hoplimit 4294967295 fe80::/64 dev eth0 proto kernel metric 256 mtu 8950 advmss 8890 hoplimit 4294967295 fe80::/64 dev vlan764 proto kernel metric 256 mtu 8950 advmss 8890 hoplimit 4294967295 default via fe80::226:bff:fe29:c40 dev vlan764 proto kernel metric 1024 expires 0sec mtu 8950 advmss 8890 hoplimit 64 Now `expire` is gone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/917643 Title: Adding address to vlan in UNKNOWN state results in routes that expire within 30 days. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/917643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 908981] Re: SRU: Bump KVM_MAX_VCPUS to 64
** Description changed: SRU Justification: There are lots of server boxes with more than 16 CPUs. Current KVM implementation can give up to 16 vCPUs to guest system. It would be nice if we could rise this limit. Upstream commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=0680fe52753381cb7154beeb01ef3e48f2cdeec6 + + PS. Also backporting of fix should require original SRCU patchset from + 2.6.34 to be ported as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/908981 Title: SRU: Bump KVM_MAX_VCPUS to 64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/908981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 908981] Re: SRU: Bump KVM_MAX_VCPUS to 64
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/908981 Title: SRU: Bump KVM_MAX_VCPUS to 64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/908981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 908981] [NEW] SRU: Bump KVM_MAX_VCPUS to 64
Public bug reported: SRU Justification: There are lots of server boxes with more than 16 CPUs. Current KVM implementation can give up to 16 vCPUs to guest system. It would be nice if we could rise this limit. Upstream commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=0680fe52753381cb7154beeb01ef3e48f2cdeec6 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/908981 Title: SRU: Bump KVM_MAX_VCPUS to 64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/908981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 908981] Re: SRU: Bump KVM_MAX_VCPUS to 64
** Attachment added: "0001-KVM-Bump-maximum-vcpu-count-to-64.patch" https://bugs.launchpad.net/bugs/908981/+attachment/2648033/+files/0001-KVM-Bump-maximum-vcpu-count-to-64.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/908981 Title: SRU: Bump KVM_MAX_VCPUS to 64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/908981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 705509] Re: /dev/kvm is owned by root:root after install on natty
Will it be ported to lucid? ** Also affects: qemu-kvm Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/705509 Title: /dev/kvm is owned by root:root after install on natty To manage notifications about this bug go to: https://bugs.launchpad.net/qemu-kvm/+bug/705509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 790863] Re: Unable to start lxc container after update to 2.6.32-32
>> Where have all my testers gone? This patch isn't going in without some >> feedback. Hmm.. Half a year... To Debian I guess -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 614322] Re: libvirt not recognizing NUMA architecture
Any progress after two weeks? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/614322 Title: libvirt not recognizing NUMA architecture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/614322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 582769] Re: /lib/security/pam_cap.so: undefined symbol: pam_get_item
I think it has even greater impact: pam module is not working so we can't set per-user inheritable capabilities via /etc/security/capability.conf in common-auth -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/582769 Title: /lib/security/pam_cap.so: undefined symbol: pam_get_item To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/582769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 582769] Re: /lib/security/pam_cap.so: undefined symbol: pam_get_item
Is it going to be backported to LTS? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/582769 Title: /lib/security/pam_cap.so: undefined symbol: pam_get_item To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/582769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839630] Re: proc: make /proc/pid/limits world readable
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839630 Title: proc: make /proc/pid/limits world readable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/839630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839630] [NEW] proc: make /proc/pid/limits world readable
Public bug reported: Having the limits file world readable will ease the task of system management on systems where root privileges might be restricted. Having admin restricted with root priviledges, he/she could not check other users process' limits. Also it'd align with most of the /proc stat files. Via http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=3036e7b490bf7878c6dae952eec5fb87b1106589 Can this patch be applied to Ubuntu 10.04 LTS ? ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839630 Title: proc: make /proc/pid/limits world readable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/839630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 804355] [NEW] jot random number generator broken in batch jobs
Public bug reported: jot -r generates same random numbers within one second time so it's unusable in batch jobs like shell scripts. There is code for initializing "random" seed: s = (randomize ? time(0) : STEP_DEF); /*... snip */ srand((int) s); Here is an example of this behavior: rbtz@rbtz-desktop:~$ date +%s; jot -r 1 0 1000 1309455778 9981995 rbtz@rbtz-desktop:~$ date +%s; jot -r 1 0 1000 1309455779 2355993 rbtz@rbtz-desktop:~$ date +%s; jot -r 1 0 1000 1309455779 2355993 rbtz@rbtz-desktop:~$ date +%s; jot -r 1 0 1000 1309455779 2355993 rbtz@rbtz-desktop:~$ date +%s; jot -r 1 0 1000 1309455780 3745306 rbtz@rbtz-desktop:~$ date +%s; jot -r 1 0 1000 1309455780 3745306 As fast fix pid can be added to seed srandom((int) s ^ (getpid()<<4)); As good fix arc4random or similar mechanism can be used. ** Affects: athena-jot (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/804355 Title: jot random number generator broken in batch jobs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/athena-jot/+bug/804355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 796937] Re: Disable CONFIG_NET_NS (for #720095) breaks LXC
*** This bug is a duplicate of bug 790863 *** https://bugs.launchpad.net/bugs/790863 ** This bug has been marked a duplicate of bug 790863 Unable to start lxc container after update to 2.6.32-32 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/796937 Title: Disable CONFIG_NET_NS (for #720095) breaks LXC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/796937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 796993] Re: Disable CONFIG_NET_NS (for #720095) breaks LXC
*** This bug is a duplicate of bug 790863 *** https://bugs.launchpad.net/bugs/790863 ** This bug is no longer a duplicate of bug 796937 Disable CONFIG_NET_NS (for #720095) breaks LXC ** This bug has been marked a duplicate of bug 790863 Unable to start lxc container after update to 2.6.32-32 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/796993 Title: Disable CONFIG_NET_NS (for #720095) breaks LXC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/796993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
