Where did this get stuck?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/994931
Title:
Altering use_tempaddr drops all IPv6 addresses
Status in Linux:
Invalid
Status in linux package
Thanks, Kamal!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/994931
Title:
Altering use_tempaddr drops all IPv6 addresses
Status in Linux:
Invalid
Status in linux package in Ubuntu:
Verified on trusty. Unfortunately I don't have a precise machine
anymore. After toggling use_tempaddr not all public addresses
disappeared with the new kernel while it happened with the old pre-
reboot.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You
Adding Timo explicitly who said in
https://bugs.launchpad.net/ubuntu/+source/linux-
firmware/+bug/1624164/comments/5 that kbl_dmc is optional and for power
saving, but skl_guc_ver6 is actually needed on Skylake. Skylake devices
are what we have and which don't properly work without the firmware.
*** This bug is a security vulnerability ***
Public security bug reported:
To enable kexec makes sense for a generic distro kernel. But if your
users have root and you want to make it hard for them to run code in
ring 0, you commonly disable further module loading and you also want to
disable
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1221995
Title:
Bluetooth Dongle (Cambridge Silicon Radio, Ltd) doesnt
It seems that my patch was applied in the wrong place. You put it after
the 4th arg instead of after %rsi is written (easy to miss given the
vastly different assembly argument orders). We actually need to fix up
%rsi / 2nd arg syscall number and instead it is now overwritten by the
movq %rax,%rsi
Sadly we need a second patch, after which it runs stable in my testing.
I'm not into the intrinsic details of x32, but apparently the syscalls
come in through both the 64bit and 32bit paths, which I find a bit
weird. (At least my first patch made it occur significantly less often.)
Patch attached
So the IPv6 support works as expected as soon as you enable
CONFIG_IP_VS_IPV6=y in the kernel config and recompile it. This is an
issue purely in the kernel and not in ipvsadm. I'd like to ask the
kernel maintainers to turn on that configuration option, as it also
breaks IPv6 load balancing using
There is no crash to collect and this is a feature request to reenable
something that was apparently enabled before and then broke.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is
CVE-2014-3917 has been assigned to this issue: http://seclists.org/oss-
sec/2014/q2/377
Another proposed patch for this has been posted here:
http://article.gmane.org/gmane.linux.kernel/1713179 — This one adds a
guard around the array access but also drops syscall auditing for x32
calls.
** CVE
This is not HP-specific and also happens on Dell HW. I'll take this as
the tracking bug. This commit suggests that the BUG_ON is actually
bogus:
http://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?id=107437febd495a50e2cd09c81bbaa84d30e57b07
In the referenced thread there was a Cc to
The following might help (untested, as root):
echo never /sys/kernel/mm/transparent_hugepage/enabled
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1323165
Title:
[HP ProLiant DL380p
Did the workaround work?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1323165
Title:
[HP ProLiant DL380p Gen8] kernel BUG at
/build/buildd/linux-3.13.0/mm/memory.c:3756!
Status in
Dave, when is this change going out approximately?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1300739
Title:
keepalived doesn't load any ipv6 virtual servers
Status in Keepalived.
The commit removing the BUG_ON landed upstream in 3.16 (linus/master).
commit 107437febd495a50e2cd09c81bbaa84d30e57b07
Author: Rik van Riel r...@redhat.com
Date: Tue Apr 29 15:36:15 2014 -0400
mm/numa: Remove BUG_ON() in __handle_mm_fault()
Changing PTEs and PMDs to pte_numa
The following commit landed upstream that at least intends to fix the
bug outlined here, even though it does not enable proper auditing for
x32.
commit a3c54931199565930d6d84f4c3456f6440aefd41
Author: Andy Lutomirski l...@amacapital.net
Date: Wed May 28 23:09:58 2014 -0400
auditsc:
This should also go into precise-proposed through the LTS backport. I
mainly need it there. ;-)
I installed the trusty kernel from -proposed on precise directly and it
works.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
FWIW, it's 3.13.0-30-generic with 3.13.0-30.54.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1300739
Title:
keepalived doesn't load any ipv6 virtual servers
Status in Keepalived.
Thanks, Dave. I'm deploying it from there then. :)
@dkpeall: It's in trusty-proposed, too.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1300739
Title:
keepalived doesn't load any
Could this be enabled in the saucy LTS backport kernel in precise as
well, please? It will take a while until the trusty kernel becomes
available there and this blocks our switch to the saucy kernel. Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which
Also I want to make the point, even if it can possibly be discarded
quickly, that the saucy stack is, to my knowledge, not supported yet on
precise. So changes in there could be held to a different standard than
in saucy proper. But I sort of understand if you avoid divergence
between saucy's
Oh ok. I was under the impression that it was only supported from
12.04.4, to be released in a week or two.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1244627
Title:
Please enable
Trying to kexec with the sysctl enabled correctly gives kexec_load
failed: Operation not permitted. Re-enabling it does not work, as
expected. With the sysctl untouched kexec works just fine.
** Tags removed: verification-needed-saucy
** Tags added: verification-done-saucy
--
You received this
Public bug reported:
The trusty kernel misses the following patch that already landed in
utopic with the recent aufs update:
https://github.com/sfjro/aufs3-linux/commit/7aac34b421441b701cd0e6de4685b51e4c462d67
This unbreaks aufs with IMA (Integrity Measurement Architecture)
enabled. When IMA is
I confirm that the patched kernel fixes the issue. Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1371316
Title:
Please cherry-pick an aufs patch to unbreak it in conjunction
I don't see it in 3.13.11.7 nor in the 3.13.y queue. Are you sure that
it'll make it?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1368444
Title:
Add support for ForcePads found on HP
Did this also miss the current cycle?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1371316
Title:
Please cherry-pick an aufs patch to unbreak it in conjunction with IMA
Status in
Reproduced with our configuration before (broken) and after (working).
Looks good to me, thanks!
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Public bug reported:
https://access.redhat.com/solutions/720473 still applies to the trusty
kernel. In fact https://lists.ubuntu.com/archives/kernel-
team/2014-July/045459.html did apply one of the two patches to 3.11, but
it was not applied to 3.13 and is not present in master-next. The other
Seems fixed in -26. That one didn't crash for me yet while -25 crashed
within hours. The changelog looks quite horrible to me with quite a few
memory corruptions, including thp (on always for me), compound page
freeing, FUSE, and vfs. Let's close this unless I see it again on -26.
** Changed in:
What's the ETA for trusty?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1450442
Title:
Kernel Oops - unable to handle kernel NULL pointer dereference at
(null); Call Trace:
Public bug reported:
Looking at linux-image-extra-3.19.0-18-generic here, but I expect this
to be pretty pervasive. This is its postrm:
#!/bin/sh
set -e
case $0::$1 in
*.postinst::configure|*.postrm::remove)
depmod -a -F /boot/System.map-3.19.0-18-generic 3.19.0-18-generic ||
true
This is a straightforward coding error that does not require any logs.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
It'd be helpful if this memory corruption regression could be
accelerated. It means that unplugging a USB3 device can mess up the
memory enough that file lookups that happen afterwards break if apparmor
is enabled - just because the allocation size is similar by chance. The
resulting oops is very
35 matches
Mail list logo
