Maybe this is the fix:
x86/speculation/l1tf: fix overflow on l1tf_pfn_limit() on 32bit
https://lkml.org/lkml/2018/8/20/222
--
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/1788321
Title:
s
On Xenial, update to "linux-image-4.4.0-135-generic 4.4.0-135.161" did
not fix the problem, but I noticed a message, that might be related to
the issue:
[3.083083] Truncating oversized swap area, only using 0k out of
261116k
--
You received this bug notification because you are a member of K
This is the failing "swapon" sequence from updated Xenial i386 on
vmware:
3915 open("/dev/sda2", O_RDONLY|O_LARGEFILE) = 3
3915 uname({sysname="Linux", nodename="v3ls1717", ...}) = 0
3915 ioctl(3, BLKGETSIZE64, [535822336]) = 0
3915 read(3,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\
Re-reported via apport/ubuntu-bug, see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586997
--
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/1508737
Title:
unix domain socket bind
** Information type changed from Public to Public Security
--
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/1508737
Title:
unix domain socket bind causes kernel audit NULL pointer deferenc
Rediscovered also on our systems, then found this bug report.
Reproducer for Ubuntu Trusty LTS:
auditctl -a always,exit -F arch=b64 -S bind
#!/usr/bin/python2 -BEsSt
import socket
testSocket=socket.socket(socket.AF_UNIX, socket.SOCK_STREAM)
testSocket.bind('sock')
# dmesg -c
[ 145.499064] BUG:
*** This bug is a duplicate of bug 1450442 ***
https://bugs.launchpad.net/bugs/1450442
Sorry, was too fast. The patch works with some audit rulesets, but not
all.
And here is also the new OOPS for amd64:
[ 424.803949] BUG: unable to handle kernel NULL pointer dereference at
003
*** This bug is a duplicate of bug 1450442 ***
https://bugs.launchpad.net/bugs/1450442
The fix from 3.13.0-52.85 changes behavior (now SSH login working also
after first OOPS) but fix might be incomplete or there are two very
similar bugs.
New trace when using proposed:
[ 31.077681] BUG: u
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451360 is marked
as duplicate. The fix from here changes the behaviour of the duplicate
(SSH login now working again, but still kernel OOPS).
So if both have common cause (very likely), then 3.13.0-52.85 is only
incomplete fix.
--
You receive
Isn't apport for reporting of application crashes?
Apart from that sudo fails also to get privileges to access logs.
Network, X and many other command line utilities also failing, so I'm
not sure how apport could succeed.
Also syslog is crashed, the dmesg log was created manually since dmesg
and
Public bug reported:
After update, desktop and production machines, both using i386 and amd64
kernels fail.
The crash may only occur after loading of syscall audit rules, hence
boot up to initrd is still possible.
Login is still possible but many integral functions fail, e.g. sending
signals to
Just noticed, that [1] is most likely a duplicate of this.
[1] https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1317188
--
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/1158500
Title:
12 matches
Mail list logo
