from:"Philipp Kern"

[Kernel-packages] [Bug 1642709] Re: linux-firmware on Trusty is missing i915 binaries

2016-11-30 Thread Philipp Kern

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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1642709

Title:
  linux-firmware on Trusty is missing i915 binaries

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Linux-firmware is missing the following i915 firmware files, required
  by the i915 driver in 4.4.0-47-generic:

  $ update-initramfs -k 4.4.0-47-generic -c
  W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1.bin for module 
i915_bpo
  W: Possible missing firmware /lib/firmware/i915/skl_guc_ver6.bin for module 
i915_bpo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1642709/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 994931] Re: Altering use_tempaddr drops all IPv6 addresses

2016-09-27 Thread Philipp Kern

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 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:
  Confirmed
Status in linux source package in Precise:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Invalid

Bug description:
  $ uname -a
  Linux expvr-alnilam 3.2.0-24-generic-pae #37-Ubuntu SMP Wed Apr 25 10:47:59 
UTC 2012 i686 i686 i386 GNU/Linux

  $ sysctl net.ipv6.conf.eth2.use_tempaddr
  net.ipv6.conf.eth2.use_tempaddr = 2
  # (as per the default /etc/sysctl.d/10-ipv6-privacy.conf in 12.04)

  # Add a static IPv6 address:
  $ sudo ip addr add 2001:470:9321:f003::1122/64 dev eth2

  # Verify that it has been set up, and that a temporary address and a SLAAC 
address also exist:
  $ ip -6 addr list dev eth2
  4: eth2:  mtu 1500 qlen 1000
  inet6 2001:470:9321:f003:74e3:aa2b:7ee5:c002/64 scope global temporary 
dynamic 
 valid_lft 86393sec preferred_lft 14393sec
  inet6 2001:470:9321:f003:6c97:24ff:fe3f:263b/64 scope global dynamic 
 valid_lft 86393sec preferred_lft 14393sec
  inet6 2001:470:9321:f003::1122/64 scope global 
 valid_lft forever preferred_lft forever
  inet6 fe80::6c97:24ff:fe3f:263b/64 scope link 
 valid_lft forever preferred_lft forever

  # Disable RFC 4941 temporary addresses:
  $ sudo sysctl net.ipv6.conf.eth2.use_tempaddr=0
  net.ipv6.conf.eth2.use_tempaddr = 0

  $ ip -6 addr list dev eth2
  4: eth2:  mtu 1500 qlen 1000
  inet6 fe80::6c97:24ff:fe3f:263b/64 scope link tentative 
 valid_lft forever preferred_lft forever

  I.e. on setting use_tempaddr=0, _all_ IPv6 addresses are removed,
  including statically-configured and non-temporary SLAAC-configured
  addresses.  (The link-local address reappears quickly but the
  'tentative' flag indicates that it has been newly re-added.  The SLAAC
  address reappears after a slightly longer interval as the kernel
  continues to undergo SLAAC, but the static address is gone forever
  unless manually reinstated.)

  The same happens if use_tempaddr is changed from 0 back to 2.

  The expected outcome is that only temporary addresses are affected by a 
change to use_tempaddr.
  --- 
  AcpiTables:
   
  AlsaDevices:
   total 0
   crw-rw---T 1 root audio 116,  1 May  5 03:53 seq
   crw-rw---T 1 root audio 116, 33 May  5 03:53 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   
  DistroRelease: Ubuntu 12.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen.linux
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: root=UUID=b16ffd9c-a54a-4dd3-a839-16c382ea8787 ro  
console=hvc0
  ProcModules:
   lp 17455 0 - Live 0x
   parport 40930 1 lp, Live 0x
   xenfs 17877 1 - Live 0x
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-24-generic-pae N/A
   linux-backports-modules-3.2.0-24-generic-pae  N/A
   linux-firmware1.79
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  precise
  Uname: Linux 3.2.0-24-generic-pae i686
  UpgradeStatus: Upgraded to precise on 2012-05-05 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/994931/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 994931] Re: Altering use_tempaddr drops all IPv6 addresses

2016-09-16 Thread Philipp Kern

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:
  Confirmed
Status in linux source package in Precise:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Utopic:
  Invalid

Bug description:
  $ uname -a
  Linux expvr-alnilam 3.2.0-24-generic-pae #37-Ubuntu SMP Wed Apr 25 10:47:59 
UTC 2012 i686 i686 i386 GNU/Linux

  $ sysctl net.ipv6.conf.eth2.use_tempaddr
  net.ipv6.conf.eth2.use_tempaddr = 2
  # (as per the default /etc/sysctl.d/10-ipv6-privacy.conf in 12.04)

  # Add a static IPv6 address:
  $ sudo ip addr add 2001:470:9321:f003::1122/64 dev eth2

  # Verify that it has been set up, and that a temporary address and a SLAAC 
address also exist:
  $ ip -6 addr list dev eth2
  4: eth2:  mtu 1500 qlen 1000
  inet6 2001:470:9321:f003:74e3:aa2b:7ee5:c002/64 scope global temporary 
dynamic 
 valid_lft 86393sec preferred_lft 14393sec
  inet6 2001:470:9321:f003:6c97:24ff:fe3f:263b/64 scope global dynamic 
 valid_lft 86393sec preferred_lft 14393sec
  inet6 2001:470:9321:f003::1122/64 scope global 
 valid_lft forever preferred_lft forever
  inet6 fe80::6c97:24ff:fe3f:263b/64 scope link 
 valid_lft forever preferred_lft forever

  # Disable RFC 4941 temporary addresses:
  $ sudo sysctl net.ipv6.conf.eth2.use_tempaddr=0
  net.ipv6.conf.eth2.use_tempaddr = 0

  $ ip -6 addr list dev eth2
  4: eth2:  mtu 1500 qlen 1000
  inet6 fe80::6c97:24ff:fe3f:263b/64 scope link tentative 
 valid_lft forever preferred_lft forever

  I.e. on setting use_tempaddr=0, _all_ IPv6 addresses are removed,
  including statically-configured and non-temporary SLAAC-configured
  addresses.  (The link-local address reappears quickly but the
  'tentative' flag indicates that it has been newly re-added.  The SLAAC
  address reappears after a slightly longer interval as the kernel
  continues to undergo SLAAC, but the static address is gone forever
  unless manually reinstated.)

  The same happens if use_tempaddr is changed from 0 back to 2.

  The expected outcome is that only temporary addresses are affected by a 
change to use_tempaddr.
  --- 
  AcpiTables:
   
  AlsaDevices:
   total 0
   crw-rw---T 1 root audio 116,  1 May  5 03:53 seq
   crw-rw---T 1 root audio 116, 33 May  5 03:53 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   
  DistroRelease: Ubuntu 12.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen.linux
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: root=UUID=b16ffd9c-a54a-4dd3-a839-16c382ea8787 ro  
console=hvc0
  ProcModules:
   lp 17455 0 - Live 0x
   parport 40930 1 lp, Live 0x
   xenfs 17877 1 - Live 0x
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-24-generic-pae N/A
   linux-backports-modules-3.2.0-24-generic-pae  N/A
   linux-firmware1.79
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  precise
  Uname: Linux 3.2.0-24-generic-pae i686
  UpgradeStatus: Upgraded to precise on 2012-05-05 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/994931/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 994931] Re: Altering use_tempaddr drops all IPv6 addresses

2016-09-05 Thread Philipp Kern

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 in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Utopic:
  Invalid

Bug description:
  $ uname -a
  Linux expvr-alnilam 3.2.0-24-generic-pae #37-Ubuntu SMP Wed Apr 25 10:47:59 
UTC 2012 i686 i686 i386 GNU/Linux

  $ sysctl net.ipv6.conf.eth2.use_tempaddr
  net.ipv6.conf.eth2.use_tempaddr = 2
  # (as per the default /etc/sysctl.d/10-ipv6-privacy.conf in 12.04)

  # Add a static IPv6 address:
  $ sudo ip addr add 2001:470:9321:f003::1122/64 dev eth2

  # Verify that it has been set up, and that a temporary address and a SLAAC 
address also exist:
  $ ip -6 addr list dev eth2
  4: eth2:  mtu 1500 qlen 1000
  inet6 2001:470:9321:f003:74e3:aa2b:7ee5:c002/64 scope global temporary 
dynamic 
 valid_lft 86393sec preferred_lft 14393sec
  inet6 2001:470:9321:f003:6c97:24ff:fe3f:263b/64 scope global dynamic 
 valid_lft 86393sec preferred_lft 14393sec
  inet6 2001:470:9321:f003::1122/64 scope global 
 valid_lft forever preferred_lft forever
  inet6 fe80::6c97:24ff:fe3f:263b/64 scope link 
 valid_lft forever preferred_lft forever

  # Disable RFC 4941 temporary addresses:
  $ sudo sysctl net.ipv6.conf.eth2.use_tempaddr=0
  net.ipv6.conf.eth2.use_tempaddr = 0

  $ ip -6 addr list dev eth2
  4: eth2:  mtu 1500 qlen 1000
  inet6 fe80::6c97:24ff:fe3f:263b/64 scope link tentative 
 valid_lft forever preferred_lft forever

  I.e. on setting use_tempaddr=0, _all_ IPv6 addresses are removed,
  including statically-configured and non-temporary SLAAC-configured
  addresses.  (The link-local address reappears quickly but the
  'tentative' flag indicates that it has been newly re-added.  The SLAAC
  address reappears after a slightly longer interval as the kernel
  continues to undergo SLAAC, but the static address is gone forever
  unless manually reinstated.)

  The same happens if use_tempaddr is changed from 0 back to 2.

  The expected outcome is that only temporary addresses are affected by a 
change to use_tempaddr.
  --- 
  AcpiTables:
   
  AlsaDevices:
   total 0
   crw-rw---T 1 root audio 116,  1 May  5 03:53 seq
   crw-rw---T 1 root audio 116, 33 May  5 03:53 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   
  DistroRelease: Ubuntu 12.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen.linux
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: root=UUID=b16ffd9c-a54a-4dd3-a839-16c382ea8787 ro  
console=hvc0
  ProcModules:
   lp 17455 0 - Live 0x
   parport 40930 1 lp, Live 0x
   xenfs 17877 1 - Live 0x
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-24-generic-pae N/A
   linux-backports-modules-3.2.0-24-generic-pae  N/A
   linux-firmware1.79
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  precise
  Uname: Linux 3.2.0-24-generic-pae i686
  UpgradeStatus: Upgraded to precise on 2012-05-05 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/994931/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1582864] Re: use after free of BOS in usb_reset_and_verify_device

2016-05-21 Thread Philipp Kern

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 misleading and it took a long time to track this
down. It also causes process hangs. 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/1582864

Title:
  use after free of BOS in usb_reset_and_verify_device

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Committed

Bug description:
  Should be fixed with upstream commit
  e5bdfd50d6f76077bf8441d130c606229e100d40, which reverts upstream
  commit d8f00cd685f5c8e0def8593e520a7fef12c22407.

  With slub_debug enabled this manifests as a deref of 0x6b6b... in
  usb_disable_ltm

  [  218.235302] general protection fault:  [#1] SMP 
  [  218.235311] Modules linked in: usb_storage tcp_diag inet_diag iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_filter 
ip_tables x_tables autofs4 rpcsec_gss_krb5 rfcomm bnep bluetooth 
snd_hda_codec_hdmi binfmt_misc nvidia(POX) snd_hda_codec_realtek snd_hda_intel 
snd_usb_audio snd_hda_codec snd_usbmidi_lib uvcvideo videobuf2_vmalloc 
videobuf2_memops videobuf2_core snd_hwdep snd_seq_midi joydev snd_pcm videodev 
snd_page_alloc snd_seq_midi_event nfsd snd_rawmidi snd_seq auth_rpcgss 
parport_pc nfs_acl ppdev nfs lockd sunrpc fscache honeevent(OX) snd_seq_device 
snd_timer snd drm lp parport sb_edac mei_me hp_wmi sparse_keymap gpio_ich 
hpuefi(OX) intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm soundcore edac_core mei serio_raw tpm_infineon lpc_ich mac_hid wmi shpchp 
dm_crypt hid_generic usbhid hid crct10dif_pclmul crc32_pclmul aesni_intel 
aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse isci e1000e ahci 
libsas lib
 ahci ptp pps_core scsi_transport_sas pata_acpi
  [  218.235410] CPU: 15 PID: 243 Comm: khubd Tainted: P   OX 
3.13.0-85-generic #129-Ubuntu
  [  218.235414] Hardware name: Hewlett-Packard HP Z620 Workstation/158A, BIOS 
J61 v03.87 02/09/2015
  [  218.235418] task: 8807eff98000 ti: 8807effa task.ti: 
8807effa
  [  218.235421] RIP: 0010:[]  [] 
usb_disable_ltm+0x56/0xb0
  [  218.235437] RSP: 0018:8807effa1cd0  EFLAGS: 00010202
  [  218.235440] RAX:  RBX: 8807ea532e68 RCX: 

  [  218.235443] RDX: 6b6b6b6b6b6b6b6b RSI: 00300021 RDI: 
8807ea532e68
  [  218.235446] RBP: 8807effa1d08 R08:  R09: 

  [  218.235449] R10: 8807ff804240 R11: 8136d2a1 R12: 

  [  218.235451] R13: 8807ebddd480 R14: 0001 R15: 
0012
  [  218.235455] FS:  () GS:88101fce() 
knlGS:
  [  218.235458] CS:  0010 DS:  ES:  CR0: 80050033
  [  218.235461] CR2: 013b1c08 CR3: 01c0e000 CR4: 
000407e0
  [  218.235463] Stack:
  [  218.235465]  81551236 8807ea532ef0  
8807ea532e68
  [  218.235476]  8807ea532ef0 8807ebddbf60  
8807effa1d48
  [  218.235483]  81545c4d 8807ea532f50 8807ebddb4d0 
02a0
  [  218.235490] Call Trace:
  [  218.235499]  [] ? usb_disable_device+0x126/0x290
  [  218.235506]  [] usb_disconnect+0xad/0x200
  [  218.235511]  [] hub_port_connect_change+0xd3/0xb20
  [  218.235518]  [] ? hub_port_status+0xdd/0x120
  [  218.235523]  [] hub_events+0x4d4/0xa20
  [  218.235528]  [] hub_thread+0x35/0x160
  [  218.235535]  [] ? prepare_to_wait_event+0x100/0x100
  [  218.235540]  [] ? hub_events+0xa20/0xa20
  [  218.235549]  [] kthread+0xd2/0xf0
  [  218.235554]  [] ? kthread_create_on_node+0x1c0/0x1c0
  [  218.235564]  [] ret_from_fork+0x58/0x90
  [  218.235570]  [] ? kthread_create_on_node+0x1c0/0x1c0
  [  218.235572] Code: e9 48 8b 52 10 48 85 d2 74 e0 f6 42 03 02 74 da 83 7f 1c 
05 75 d4 48 8b 97 40 03 00 00 48 85 d2 74 c8 48 8b 52 10 48 85 d2 74 bf  42 
03 02 74 b9 48 83 bf 50 03 00 00 00 74 af 55 45 31 c9 41 
  [  218.235618] RIP  [] usb_disable_ltm+0x56/0xb0
  [  218.235624]  RSP 
  [  218.235655] ---[ end trace 954cac763165b767 ]---

  Without slub_debug you end up getting a double free and messing up the
  allocator and apparmor tends to be the first one to notice:

  [  574.027518] hub 4-0:1.0: Cannot enable port 3.  Maybe the USB cable is bad?
  [  574.548076] usb 4-3: USB disconnect, device number 2
  [  576.040995] [ cut here ]
  [  576.041003] WARNING: CPU: 17 PID: 11627 at 
/build/linux-03BQvT/linux-3.13.0/include/linux/kref.h:47

[Kernel-packages] [Bug 1475662] Re: Kernel postrm calls /etc/kernel/postinst.d/*

2015-07-18 Thread Philipp Kern

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.
https://bugs.launchpad.net/bugs/1475662

Title:
  Kernel postrm calls /etc/kernel/postinst.d/*

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  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
  for dir in /etc/kernel/postinst.d 
/etc/kernel/postinst.d/3.19.0-18-generic
  do
  if [ -d $dir ]; then
  run-parts --verbose --exit-on-error 
--arg=3.19.0-18-generic --arg=/boot/vmlinuz-3.19.0-18-generic $dir
  fi
  done
  ;;
  esac

  As you can see it executes /etc/kernel/postinst.d/* instead of
  /etc/kernel/postrm.d/* even if it's called as a postrm script. Why?
  The problem for us is that this re-executes dkms's autoinstaller,
  which recompiles certain modules even if the kernel is being removed.
  But I find this behavior pretty surprising regardless of this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475662/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1475662] [NEW] Kernel postrm calls /etc/kernel/postinst.d/*

2015-07-17 Thread Philipp Kern

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
for dir in /etc/kernel/postinst.d 
/etc/kernel/postinst.d/3.19.0-18-generic
do
if [ -d $dir ]; then
run-parts --verbose --exit-on-error 
--arg=3.19.0-18-generic --arg=/boot/vmlinuz-3.19.0-18-generic $dir
fi
done
;;
esac

As you can see it executes /etc/kernel/postinst.d/* instead of
/etc/kernel/postrm.d/* even if it's called as a postrm script. Why? The
problem for us is that this re-executes dkms's autoinstaller, which
recompiles certain modules even if the kernel is being removed. But I
find this behavior pretty surprising regardless of this.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1475662

Title:
  Kernel postrm calls /etc/kernel/postinst.d/*

Status in linux package in Ubuntu:
  New

Bug description:
  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
  for dir in /etc/kernel/postinst.d 
/etc/kernel/postinst.d/3.19.0-18-generic
  do
  if [ -d $dir ]; then
  run-parts --verbose --exit-on-error 
--arg=3.19.0-18-generic --arg=/boot/vmlinuz-3.19.0-18-generic $dir
  fi
  done
  ;;
  esac

  As you can see it executes /etc/kernel/postinst.d/* instead of
  /etc/kernel/postrm.d/* even if it's called as a postrm script. Why?
  The problem for us is that this re-executes dkms's autoinstaller,
  which recompiles certain modules even if the kernel is being removed.
  But I find this behavior pretty surprising regardless of this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475662/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1450442] Re: Kernel Oops - unable to handle kernel NULL pointer dereference at (null); Call Trace: [ffffffff810fb39b] ? audit_compare_dname_path+0x2b/0xa0

2015-05-04 Thread Philipp Kern

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: [810fb39b] ?
  audit_compare_dname_path+0x2b/0xa0

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Utopic:
  In Progress

Bug description:
  [Impact]
  Ubuntu VMWare instances running 3.13.0-51 will crash with the following 
backtrace:

  [   12.357276] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [   12.357886] IP: [8136cb80] strlen+0x0/0x30
  [   12.358457] PGD 230fe9067 PUD 230d5c067 PMD 0
  [   12.359034] Oops:  [#1] SMP
  [   12.359590] Modules linked in: tcp_diag inet_diag vmw_vsock_vmci_transport 
vsock ip6t_REJECT xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT 
xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 
xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns 
nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack 
crct10dif_pclmul iptable_filter crc32_pclmul ip_tables ghash_clmulni_intel 
aesni_intel aes_x86_64 ppdev lrw x_tables gf128mul vmwgfx glue_helper 
ablk_helper cryptd ttm drm vmw_balloon serio_raw shpchp parport_pc lp i2c_piix4 
parport mac_hid vmw_vmci psmouse mptspi vmw_pvscsi e1000 mptscsih floppy 
vmxnet3 mptbase
  [   12.364773] CPU: 2 PID: 1718 Comm: fail2ban-server Not tainted 
3.13.0-51-generic #84-Ubuntu
  [   12.365587] Hardware name: VMware, Inc. VMware Virtual Platform/440BX 
Desktop Reference Platform, BIOS 6.00 04/14/2014
  [   12.367276] task: 880230fc3000 ti: 8802308c4000 task.ti: 
8802308c4000
  [   12.368159] RIP: 0010:[8136cb80]  [8136cb80] 
strlen+0x0/0x30
  [   12.369073] RSP: 0018:8802308c5d60  EFLAGS: 00010212
  [   12.369963] RAX: 000d RBX: 000d RCX: 
2df0
  [   12.370973] RDX: 0012 RSI:  RDI: 

  [   12.372005] RBP: 8802308c5d90 R08: 8800b9218648 R09: 
8802308c5d60
  [   12.372988] R10: 0002 R11: 88023082e180 R12: 
0012
  [   12.373901] R13:  R14: 880231f1b3f8 R15: 
8800b9218460
  [   12.374827] FS:  7f196f84c740() GS:88023fd0() 
knlGS:
  [   12.375752] CS:  0010 DS:  ES:  CR0: 80050033
  [   12.376667] CR2:  CR3: 000230872000 CR4: 
000407e0
  [   12.377684] Stack:
  [   12.378612]  810fb39b  0004 
88022ff74838
  [   12.379559]  8800b9218400 8800b9218460 8802308c5df8 
810fdb36
  [   12.380516]  811d56e0 00042ff74838 880231f1b3c0 
88022febecf8
  [   12.381506] Call Trace:
  [   12.382630]  [810fb39b] ? audit_compare_dname_path+0x2b/0xa0
  [   12.383784]  [810fdb36] __audit_inode_child+0xb6/0x330
  [   12.384912]  [811d56e0] ? d_instantiate+0x50/0x70
  [   12.386013]  [811ca060] vfs_mknod+0x110/0x160
  [   12.387145]  [816bf475] unix_bind+0x2a5/0x360
  [   12.388207]  [810ff142] ? __audit_sockaddr+0x42/0x80
  [   12.389250]  [8160d4c0] SYSC_bind+0xe0/0x120
  [   12.390297]  [8172e9fa] ? do_page_fault+0x1a/0x70
  [   12.391303]  [8160e4de] SyS_bind+0xe/0x10
  [   12.392426]  [817330bd] system_call_fastpath+0x1a/0x1f
  [   12.393581] Code: 89 f8 48 89 e5 f6 82 40 c7 84 81 20 74 15 0f 1f 44 00 00 
48 83 c0 01 0f b6 10 f6 82 40 c7 84 81 20 75 f0 5d c3 66 0f 1f 44 00 00 80 3f 
00 55 48 89 e5 74 15 48 89 f8 0f 1f 40 00 48 83 c0 01 80
  [   12.396831] RIP  [8136cb80] strlen+0x0/0x30
  [   12.397812]  RSP 8802308c5d60
  [   12.398769] CR2: 
  [   12.399743] ---[ end trace 2c5a33d31a03347e ]---

  We've also seen this on our precise machines that are running the
  backported trusty kernel.

  When reverting to kernel 3.13.0-49 this no longer occurs.

  [Test Case]
  1) Run an Ubuntu VMWare instance with the affected kernel.

  apt-get install auditd
  echo -w /etc/test /etc/audit/audit.rules
  /etc/init.d/auditd restart
  apt-get install linux-headers-3.13.0-51 linux-headers-3.13.0-51-generic 
linux-image-3.13.0-51-generic
  reboot
  attempt to login or ssh into the host - you'll get a similar stacktrace.

  
  [Fix]
  commit fcf22d8267ad2601fe9b6c549d1be96401c23e0b upstream

  --

  uname -a:
  Linux search-2 3.13.0-51-generic #84-Ubuntu SMP Wed Apr 15 12:08:34 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux

  cat /proc/version_signature:
  Ubuntu 3.13.0-51.84-generic 3.13.11-ckt18

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450442/+subscriptions

-- 
Mailing list:

[Kernel-packages] [Bug 1398465] Re: Memory allocation failure, presumably in FUSE

2014-12-08 Thread Philipp Kern

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: linux (Ubuntu)
   Status: Incomplete = Invalid

** Changed in: linux (Ubuntu)
   Status: Invalid = Won't Fix

-- 
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/1398465

Title:
  Memory allocation failure, presumably in FUSE

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  I just tried out linux-lts-utopic on trusty and hit a few backtraces.
  We make intensive use of FUSE and the FS operation I conducted on FUSE
  hung post-backtrace.

  [ 1951.617813] [ cut here ]
  [ 1951.617818] kernel BUG at 
/build/buildd/linux-lts-utopic-3.16.0/mm/slub.c:3380!
  [ 1951.617819] invalid opcode:  [#1] SMP
  [ 1951.617821] Modules linked in: des_generic nfsv3 nfsv4 vmnet(OE) 
parport_pc vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) xt_addrtype 
ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat bridge stp llc aufs netconsole 
configfs nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_NFLOG 
xt_comment xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_multiport xt_connmark 
xt_conntrack nf_conntrack xt_mark cuse iptable_filter ip_tables x_tables 
rpcsec_gss_krb5 nfnetlink_log nfnetlink autofs4 rfcomm bnep bluetooth 
6lowpan_iphc binfmt_misc snd_hda_codec_hdmi hp_wmi sparse_keymap intel_rapl 
x86_pkg_temp_thermal snd_hda_codec_realtek intel_powerclamp coretemp 
snd_hda_codec_generic kvm_intel kvm ppdev crct10dif_pclmul crc32_pclmul 
snd_hda_intel ghash_clmulni_intel aesni_intel snd_hda_controller aes_x86_64 lrw 
snd_hda_codec gf128mul glue_helper ablk_helper cryptd snd_hwdep lp snd_pcm 
parport serio_raw sb_edac edac_core snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_seq nvidia(POE) snd_se
 q_device snd_timer lpc_ich snd drm ioatdma dca soundcore wmi tpm_infineon 
mac_hid nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache nls_iso8859_1 
hid_generic usbhid hid isci firewire_ohci e1000e psmouse(OE) libsas 
firewire_core ahci libahci ptp crc_itu_t scsi_transport_sas pps_core [last 
unloaded: vmnet]
  [ 1951.617874] CPU: 2 PID: 13631 Comm: srcfsd Tainted: P   OE 
3.16.0-25-generic #33-Ubuntu
  [ 1951.617876] Hardware name: Hewlett-Packard HP Z420 Workstation/1589, BIOS 
J61 v03.65 12/19/2013
  [ 1951.617877] task: 88061f5cb2f0 ti: 880800cdc000 task.ti: 
880800cdc000
  [ 1951.617878] RIP: 0010:[811b61a3]  [811b61a3] 
kfree+0x133/0x140
  [ 1951.617884] RSP: 0018:880800cdfbf8  EFLAGS: 00010246
  [ 1951.617885] RAX: 00000400 RBX: 88007833 RCX: 
00018020001f
  [ 1951.617886] RDX: 0000 RSI: ea0002716f80 RDI: 
88007833
  [ 1951.617887] RBP: 880800cdfc10 R08: 88009c5bf400 R09: 
00018020001f
  [ 1951.617888] R10: ea0001c0 R11: 812bfd95 R12: 
8807addaf800
  [ 1951.617889] R13: 812bfda1 R14: 00020010 R15: 
880800cdfd58
  [ 1951.617890] FS:  7fccdb950700() GS:88082fc4() 
knlGS:
  [ 1951.617891] CS:  0010 DS:  ES:  CR0: 80050033
  [ 1951.617892] CR2: 08a89ff0 CR3: 0007c8fb7000 CR4: 
000407e0
  [ 1951.617893] Stack:
  [ 1951.617894]  8807a1e296c0 8807addaf800  
880800cdfc28
  [ 1951.617896]  812bfda1 8807a1e296c0 880800cdfc58 
812bfe88
  [ 1951.617897]  8807a1e296c0 8807addaf800 812c71c0 
00020010
  [ 1951.617899] Call Trace:
  [ 1951.617904]  [812bfda1] fuse_request_free+0x31/0x50
  [ 1951.617906]  [812bfe88] fuse_put_request+0xc8/0x110
  [ 1951.617908]  [812c71c0] ? fuse_short_read+0x160/0x160
  [ 1951.617910]  [812bffdc] request_end+0x10c/0x1c0
  [ 1951.617911]  [812c1436] fuse_dev_do_write+0x826/0xd10
  [ 1951.617914]  [811d36e0] ? do_sync_read+0x90/0x90
  [ 1951.617916]  [812c1c79] fuse_dev_write+0x69/0x80
  [ 1951.617918]  [811d37bc] do_sync_readv_writev+0x4c/0x80
  [ 1951.617920]  [811d510d] do_readv_writev+0x1bd/0x240
  [ 1951.617922]  [811d5219] vfs_writev+0x39/0x50
  [ 1951.617924]  [811d534a] SyS_writev+0x4a/0xd0
  [ 1951.617927]  [817690ad] system_call_fastpath+0x1a/0x1f
  [ 1951.617928] Code: 49 8b 02 31 f6 f6 c4 40 74 04 41 8b 72 68 4c 89 d7 e8 92 
3d fb ff eb 8f 4c 8b 50 30 48 8b 10 80 e6 80 4c 0f 44 d0 e9 32 ff ff ff 0f 0b 
66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 55 89 f1
  [ 1951.617946] RIP  [811b61a3] kfree+0x133/0x140
  [ 1951.617948]  RSP 880800cdfbf8
  [ 1951.617950] ---[ end trace a783e9182f5a2f00 ]---
  [ 1953.884500] general protection fault:  [#2] SMP
  [

[Kernel-packages] [Bug 1396065] [NEW] GPF in lru_put_end called from nfsd_cache_lookup

2014-11-25 Thread Philipp Kern

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
one is
http://kernel.ubuntu.com/git?p=ubuntu/linux.git;a=blobdiff;f=fs/nfsd/nfscache.c;h=e5e4675b7e755fd5c69ea52bc194a25501ef286b;hp=02e8e9ad57502fa2ff294181d6f261425bbc5969;hb=92f9180a0bdcec4a579a4b380cc0fa664f88d47d;hpb=9696a6f0ee3a1ea18b9b705a70eb76883cebe7a0
-- which also landed in 3.11 but didn't make it to 3.13.

Please apply both to fix this backtrace:

Nov 20 16:41:28 REDACTED kernel: [319683.547563] general protection fault:  
[#1] SMP 
Nov 20 16:41:28 REDACTED kernel: [319683.552668] Modules linked in: cts 
des_generic nfsv3 nfsv4 autofs4 binfmt_misc gpio_ich rpcsec_gss_krb5 nfsd 
nfs_acl auth_rpcgss nfs fscache lockd sunrpc cdc_acm sb_edac edac_core lpc_ich 
serio_raw mei_me mei mac_hid lp parport raid10 raid456 async_pq async_xor xor 
async_memcpy async_raid6_recov raid6_pq async_tx bnx2x mpt2sas raid1 ahci 
scsi_transport_sas libcrc32c libahci mdio raid_class raid0 multipath linear
Nov 20 16:41:28 REDACTED kernel: [319683.590384] CPU: 14 PID: 2576 Comm: nfsd 
Not tainted 3.13.0-39-generic #66~precise1-Ubuntu
Nov 20 16:41:28 REDACTED kernel: [319683.598737] Hardware name: REDACTED
Nov 20 16:41:28 REDACTED kernel: [319683.605802] task: 88202704b000 ti: 
882025e7a000 task.ti: 882025e7a000
Nov 20 16:41:28 REDACTED kernel: [319683.613379] RIP: 0010:[a030be70] 
 [a030be70] lru_put_end+0x20/0x70 [nfsd]
Nov 20 16:41:28 REDACTED kernel: [319683.622040] RSP: 0018:882025e7bd58  
EFLAGS: 00010206
Nov 20 16:41:28 REDACTED kernel: [319683.627440] RAX: dead00200200 RBX: 
880135386e70 RCX: dead00100100
Nov 20 16:41:28 REDACTED kernel: [319683.634654] RDX: 880135386e80 RSI: 
8802c2a9904c RDI: 880135386e70
Nov 20 16:41:28 REDACTED kernel: [319683.641878] RBP: 882025e7bd58 R08: 
88207fcd7220 R09: 88103f803b00
Nov 20 16:41:28 REDACTED kernel: [319683.649108] R10: a030c908 R11: 
00014480 R12: 882025b6a000
Nov 20 16:41:28 REDACTED kernel: [319683.656332] R13: 0002 R14: 
8802c2a9901c R15: 0030
Nov 20 16:41:28 REDACTED kernel: [319683.663565] FS:  () 
GS:88207fcc() knlGS:
Nov 20 16:41:28 REDACTED kernel: [319683.671749] CS:  0010 DS:  ES:  
CR0: 80050033
Nov 20 16:41:28 REDACTED kernel: [319683.677581] CR2: 7fc557e3b504 CR3: 
01c0d000 CR4: 000407e0
Nov 20 16:41:28 REDACTED kernel: [319683.684799] Stack:
Nov 20 16:41:28 REDACTED kernel: [319683.686913]  882025e7bda8 
a030c896 8820289c9240 0030
Nov 20 16:41:28 REDACTED kernel: [319683.694477]  a0339ff8 
882025b6a000 a0339ff8 8802c2a99018
Nov 20 16:41:28 REDACTED kernel: [319683.702026]  001c 
8802c2a99000 882025e7bde8 a0300e7a
Nov 20 16:41:28 REDACTED kernel: [319683.709575] Call Trace:
Nov 20 16:41:28 REDACTED kernel: [319683.712132]  [a030c896] 
nfsd_cache_update+0x86/0x150 [nfsd]
Nov 20 16:41:28 REDACTED kernel: [319683.718653]  [a0300e7a] 
nfsd_dispatch+0x1ba/0x230 [nfsd]
Nov 20 16:41:28 REDACTED kernel: [319683.724936]  [a0238565] 
svc_process_common+0x345/0x680 [sunrpc]
Nov 20 16:41:28 REDACTED kernel: [319683.731812]  [a0238bf3] 
svc_process+0x103/0x160 [sunrpc]
Nov 20 16:41:28 REDACTED kernel: [319683.738084]  [a03008ff] 
nfsd+0xbf/0x130 [nfsd]
Nov 20 16:41:28 REDACTED kernel: [319683.743490]  [a0300840] ? 
nfsd_destroy+0x80/0x80 [nfsd]
Nov 20 16:41:28 REDACTED kernel: [319683.749679]  [8108fb29] 
kthread+0xc9/0xe0
Nov 20 16:41:28 REDACTED kernel: [319683.754640]  [8108fa60] ? 
flush_kthread_worker+0xb0/0xb0
Nov 20 16:41:28 REDACTED kernel: [319683.760932]  [8176b5bc] 
ret_from_fork+0x7c/0xb0
Nov 20 16:41:28 REDACTED kernel: [319683.766417]  [8108fa60] ? 
flush_kthread_worker+0xb0/0xb0
Nov 20 16:41:28 REDACTED kernel: [319683.772697] Code: 5b 5d c3 0f 1f 84 00 00 
00 00 00 66 66 66 66 90 48 8b 05 a4 11 a1 e1 55 48 8d 57 10 48 8b 4f 10 48 89 
e5 48 89 47 58 48 8b 47 18 48 89 41 08 48 89 08 b9 30 75 00 00 48 8b 05 55 0d 
03 00 48 c7 
Nov 20 16:41:28 REDACTED kernel: [319683.792771] RIP  [a030be70] 
lru_put_end+0x20/0x70 [nfsd]
Nov 20 16:41:28 REDACTED kernel: [319683.799061]  RSP 882025e7bd58
Nov 20 16:41:28 REDACTED kernel: [319683.802679] ---[ end trace 
e4c61e4b0608416b ]---

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux-lts-trusty (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Trusty)
 Importance: Undecided
 Status: New

** Affects: linux-lts-trusty (Ubuntu Trusty)
 Importance: Undecided

[Kernel-packages] [Bug 1371316] Re: Please cherry-pick an aufs patch to unbreak it in conjunction with IMA

2014-10-17 Thread Philipp Kern

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 Ubuntu.
https://bugs.launchpad.net/bugs/1371316

Title:
  Please cherry-pick an aufs patch to unbreak it in conjunction with IMA

Status in “linux” package in Ubuntu:
  Invalid
Status in “linux-lts-trusty” package in Ubuntu:
  Invalid
Status in “linux” source package in Precise:
  Invalid
Status in “linux-lts-trusty” source package in Precise:
  In Progress
Status in “linux” source package in Trusty:
  Fix Committed
Status in “linux-lts-trusty” source package in Trusty:
  Invalid

Bug description:
  SRU justification

  Impact: when using IMA with aufs in trusty potential exists for very
  hard to diagnose lockups.

  Testcase: enable IMA and use an aufs filesystem.

  Regression Potential: the fix is an upstream cherry-pick from the version of
  aufs in Utopic which is used widly for lxc there so regression potential is 
low.  The fix removes code which also lessens the risk.

  ===

  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 enabled and mmaps are being tracked, the kernel
  hits a lock ordering bug because a needed semaphore is already held.
  This patch fixes this issue by not calling out to IMA for the access
  to the underlying file. However IMA will still see the access to the
  file in the merged aufs, which should be good enough.

  Please cherry-pick above patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371316/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1371316] Re: Please cherry-pick an aufs patch to unbreak it in conjunction with IMA

2014-09-24 Thread Philipp Kern

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 “linux” package in Ubuntu:
  Invalid
Status in “linux-lts-trusty” package in Ubuntu:
  Invalid
Status in “linux” source package in Precise:
  Invalid
Status in “linux-lts-trusty” source package in Precise:
  In Progress
Status in “linux” source package in Trusty:
  Fix Committed
Status in “linux-lts-trusty” source package in Trusty:
  Invalid

Bug description:
  SRU justification

  Impact: when using IMA with aufs in trusty potential exists for very
  hard to diagnose lockups.

  Testcase: enable IMA and use an aufs filesystem.

  Regression Potential: the fix is an upstream cherry-pick from the version of
  aufs in Utopic which is used widly for lxc there so regression potential is 
low.  The fix removes code which also lessens the risk.

  ===

  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 enabled and mmaps are being tracked, the kernel
  hits a lock ordering bug because a needed semaphore is already held.
  This patch fixes this issue by not calling out to IMA for the access
  to the underlying file. However IMA will still see the access to the
  file in the merged aufs, which should be good enough.

  Please cherry-pick above patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371316/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1368444] Re: Add support for ForcePads found on HP EliteBook Folio 1040

2014-09-23 Thread Philipp Kern

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 EliteBook Folio 1040

Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  Please include the following commit from mainline in Ubuntu kernel:

  From 5715fc764f7753d464dbe094b5ef9cffa6e479a4 Mon Sep 17 00:00:00 2001
  From: Dmitry Torokhov dmitry.torok...@gmail.com
  Date: Sat, 30 Aug 2014 13:51:06 -0700
  Subject: Input: synaptics - add support for ForcePads

  ForcePads are found on HP EliteBook 1040 laptops. They lack any kind of
  physical buttons, instead they generate primary button click when user
  presses somewhat hard on the surface of the touchpad. Unfortunately they
  also report primary button click whenever there are 2 or more contacts
  on the pad, messing up all multi-finger gestures (2-finger scrolling,
  multi-finger tapping, etc). To cope with this behavior we introduce a
  delay (currently 50 msecs) in reporting primary press in case more
  contacts appear.

  Cc: sta...@vger.kernel.org
  Reviewed-by: Hans de Goede hdego...@redhat.com
  Signed-off-by: Dmitry Torokhov dmitry.torok...@gmail.com

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1368444/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1371316] Re: Please cherry-pick an aufs patch to unbreak it in conjunction with IMA

2014-09-22 Thread Philipp Kern

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 with IMA

Status in “linux” package in Ubuntu:
  Invalid
Status in “linux-lts-trusty” package in Ubuntu:
  Invalid
Status in “linux” source package in Precise:
  Invalid
Status in “linux-lts-trusty” source package in Precise:
  In Progress
Status in “linux” source package in Trusty:
  In Progress
Status in “linux-lts-trusty” source package in Trusty:
  Invalid

Bug description:
  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 enabled and mmaps are being tracked, the kernel
  hits a lock ordering bug because a needed semaphore is already held.
  This patch fixes this issue by not calling out to IMA for the access
  to the underlying file. However IMA will still see the access to the
  file in the merged aufs, which should be good enough.

  Please cherry-pick above patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371316/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1371316] [NEW] Please cherry-pick an aufs patch to unbreak it in conjunction with IMA

2014-09-18 Thread Philipp Kern

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 enabled and mmaps are being tracked, the kernel
hits a lock ordering bug because a needed semaphore is already held.
This patch fixes this issue by not calling out to IMA for the access to
the underlying file. However IMA will still see the access to the file
in the merged aufs, which should be good enough.

Please cherry-pick above patch.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

** Affects: linux-lts-trusty (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: linux-lts-trusty (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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 “linux” package in Ubuntu:
  Incomplete
Status in “linux-lts-trusty” package in Ubuntu:
  New

Bug description:
  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 enabled and mmaps are being tracked, the kernel
  hits a lock ordering bug because a needed semaphore is already held.
  This patch fixes this issue by not calling out to IMA for the access
  to the underlying file. However IMA will still see the access to the
  file in the merged aufs, which should be good enough.

  Please cherry-pick above patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371316/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1300739] Re: keepalived doesn't load any ipv6 virtual servers

2014-06-13 Thread Philipp Kern

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 ipv6 virtual servers

Status in Keepalived. Loadbalancing  High-Avaibility:
  New
Status in “keepalived” package in Ubuntu:
  Invalid
Status in “linux” package in Ubuntu:
  Fix Released
Status in “keepalived” source package in Trusty:
  Invalid
Status in “linux” source package in Trusty:
  Fix Committed
Status in “keepalived” source package in Utopic:
  Invalid
Status in “linux” source package in Utopic:
  Fix Released

Bug description:
  SRU Justification:
  Impact: Keepalived is no longer able to load any IPv6 virtual servers for 
load balancing purposes.
  Fix: Re-enable CONFIG_IP_VS_IPV6=y
  Testcase: Attempt to load ipv6 virtual servers.


  _

  
  I've upgraded from 12.04 to 14.04 and the keepalived no longer loads any IPv6 
virtual servers.

  I get the following message when trying to list a virtual service:
  ipvsadm -L -t [2001::::xxx]:xxx
  Resource temporarily unavailable

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: keepalived 1:1.2.7-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  Date: Tue Apr  1 13:45:51 2014
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SourcePackage: keepalived
  UpgradeStatus: Upgraded to trusty on 2014-03-31 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/keepalived/+bug/1300739/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1302605] Re: Calls to /libx32/ld-linux-x32.so.2 hang when using auditd

2014-06-12 Thread Philipp Kern

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: audit_krule mask accesses need bounds checking

Fixes an easy DoS and possible information disclosure.

This does nothing about the broken state of x32 auditing.

eparis: If the admin has enabled auditd and has specifically loaded
audit rules.  This bug has been around since before git.  Wow...

Cc: sta...@vger.kernel.org
Signed-off-by: Andy Lutomirski l...@amacapital.net
Signed-off-by: Eric Paris epa...@redhat.com
Signed-off-by: Linus Torvalds torva...@linux-foundation.org

-- 
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/1302605

Title:
  Calls to /libx32/ld-linux-x32.so.2 hang when using auditd

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux” source package in Trusty:
  New

Bug description:
  I'm running trusty on a bunch of machines, doing frequent dist-
  upgrades.  My hosts have gcc-multilib installed.

  Yesterday, I noticed that initramfs generation was hanging.  Today I
  investigated further and found out that what was hanging were the
  calls to /libx32/ld-linux-x32.so.2.

  This is triggered in initramfs generation because there are at some
  hooks that incorrectly use copy_exec to copy shell scripts into the
  initramfs image.  In a working machine, when ldd encounters a shell
  script, it will first call the 64bit linker and since it fails, it
  will then call the 32bit linker which will also fail.

  However, in a machine affected by this bug, the second call will hang
  forever, preventing new image generation, and package updates in
  general, when this happens as a trigger for update-initramfs.

  Originally I thought this was related to the kernel version, since I
  was unable to reproduce in a freshly installed machine running -22 and
  was reproducing it in a machine running -20, but now I'm also
  reproducing it in a machine running -22, so it must be something else.

  I'm sorry I can't provide the exact cause right now, but I think it's
  worth noting that in some situation there might be a problem, and try
  to find out which those situations are.

  I now have one host running 3.13.0-22-generic, with
  libc6-x32=2.19-0ubuntu3, where doing ldd /usr/bin/ldd hangs, and
  another host, with the exact same kernel and libc6-x32 version where
  doing ldd /usr/bin/ldd produces the expected error message (not a
  dynamic executable).  The main difference is that the first one was
  installed yesterday and the second one was installed today.  Both are
  dist-upgraded to the latest version of everything.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1302605/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1300739] Re: keepalived doesn't load any ipv6 virtual servers

2014-06-12 Thread Philipp Kern

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 Ubuntu.
https://bugs.launchpad.net/bugs/1300739

Title:
  keepalived doesn't load any ipv6 virtual servers

Status in Keepalived. Loadbalancing  High-Avaibility:
  New
Status in “keepalived” package in Ubuntu:
  Invalid
Status in “linux” package in Ubuntu:
  Fix Released
Status in “keepalived” source package in Trusty:
  New
Status in “linux” source package in Trusty:
  Fix Committed
Status in “keepalived” source package in Utopic:
  Invalid
Status in “linux” source package in Utopic:
  Fix Released

Bug description:
  SRU Justification:
  Impact: Keepalived is no longer able to load any IPv6 virtual servers for 
load balancing purposes.
  Fix: Re-enable CONFIG_IP_VS_IPV6=y
  Testcase: Attempt to load ipv6 virtual servers.


  _

  
  I've upgraded from 12.04 to 14.04 and the keepalived no longer loads any IPv6 
virtual servers.

  I get the following message when trying to list a virtual service:
  ipvsadm -L -t [2001::::xxx]:xxx
  Resource temporarily unavailable

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: keepalived 1:1.2.7-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  Date: Tue Apr  1 13:45:51 2014
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SourcePackage: keepalived
  UpgradeStatus: Upgraded to trusty on 2014-03-31 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/keepalived/+bug/1300739/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1300739] Re: keepalived doesn't load any ipv6 virtual servers

2014-06-12 Thread Philipp Kern

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. Loadbalancing  High-Avaibility:
  New
Status in “keepalived” package in Ubuntu:
  Invalid
Status in “linux” package in Ubuntu:
  Fix Released
Status in “keepalived” source package in Trusty:
  New
Status in “linux” source package in Trusty:
  Fix Committed
Status in “keepalived” source package in Utopic:
  Invalid
Status in “linux” source package in Utopic:
  Fix Released

Bug description:
  SRU Justification:
  Impact: Keepalived is no longer able to load any IPv6 virtual servers for 
load balancing purposes.
  Fix: Re-enable CONFIG_IP_VS_IPV6=y
  Testcase: Attempt to load ipv6 virtual servers.


  _

  
  I've upgraded from 12.04 to 14.04 and the keepalived no longer loads any IPv6 
virtual servers.

  I get the following message when trying to list a virtual service:
  ipvsadm -L -t [2001::::xxx]:xxx
  Resource temporarily unavailable

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: keepalived 1:1.2.7-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  Date: Tue Apr  1 13:45:51 2014
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SourcePackage: keepalived
  UpgradeStatus: Upgraded to trusty on 2014-03-31 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/keepalived/+bug/1300739/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1323165] Re: [HP ProLiant DL380p Gen8] kernel BUG at /build/buildd/linux-3.13.0/mm/memory.c:3756!

2014-06-10 Thread Philipp Kern

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  pmd_numa is done with the
mmap_sem held for reading, which means a pmd can be instantiated
and turned into a numa one while __handle_mm_fault() is examining
the value of old_pmd.

If that happens, __handle_mm_fault() should just return and let
the page fault retry, instead of throwing an oops. This is
handled by the test for pmd_trans_huge(*pmd) below.

Signed-off-by: Rik van Riel r...@redhat.com
Reviewed-by: Naoya Horiguchi n-horigu...@ah.jp.nec.com
Reported-by: Sunil Pandey sunil.k.pan...@intel.com
Signed-off-by: Peter Zijlstra pet...@infradead.org
Cc: Andrew Morton a...@linux-foundation.org
Cc: Johannes Weiner han...@cmpxchg.org
Cc: Kirill A. Shutemov kirill.shute...@linux.intel.com
Cc: Linus Torvalds torva...@linux-foundation.org
Cc: Mel Gorman mgor...@suse.de
Cc: linux...@kvack.org
Cc: lwood...@redhat.com
Cc: dave.han...@intel.com
Link: http://lkml.kernel.org/r/20140429153615.2d720...@annuminas.surriel.com
Signed-off-by: Ingo Molnar mi...@kernel.org

-- 
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 “linux” package in Ubuntu:
  Confirmed

Bug description:
  The machine becomes non-responsive, unable to ssh, high load average, trying 
to access the running java process does not work as per syslog:
  May 26 06:19:38 server06 kernel: [75831.929529] [ cut here 
]
  May 26 06:19:38 server06 kernel: [75831.930191] kernel BUG at 
/build/buildd/linux-3.13.0/mm/memory.c:3756!
  May 26 06:19:38 server06 kernel: [75831.931129] invalid opcode:  [#1] SMP
  May 26 06:19:38 server06 kernel: [75831.931729] Modules linked in: 
xt_multiport ip6t_REJECT xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 
ipt_REJECT xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables gpio_ich 
nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat 
nf_conntrack_ftp nf_conntrack iptable_filter ip_tables x_tables intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul 
glue_helper ablk_helper cryptd serio_raw sb_edac edac_core lpc_ich hpwdt hpilo 
ioatdma lp dca ipmi_si parport acpi_power_meter mac_hid tg3 ptp psmouse hpsa 
pps_core
  May 26 06:19:38 server06 kernel: [75831.941585] CPU: 4 PID: 2930 Comm: java 
Not tainted 3.13.0-24-generic #47-Ubuntu
  May 26 06:19:38 server06 kernel: [75831.942633] Hardware name: HP ProLiant 
DL380p Gen8, BIOS P70 02/10/2014
  May 26 06:19:38 server06 kernel: [75831.943583] task: 881fe8372fe0 ti: 
881fe632a000 task.ti: 881fe632a000
  May 26 06:19:38 server06 kernel: [75831.944654] RIP: 
0010:[81179051] [81179051] handle_mm_fault+0xe61/0xf10
  May 26 06:19:38 server06 kernel: [75831.946137] RSP: :881fe632bd98 
EFLAGS: 00010246
  May 26 06:19:38 server06 kernel: [75831.946885] RAX: 0100 RBX: 
7fc37320a370 RCX: 881fe632bb18
  May 26 06:19:38 server06 kernel: [75831.947902] RDX: 881fe8372fe0 RSI: 
 RDI: 800100c009e6
  May 26 06:19:38 server06 kernel: [75831.948932] RBP: 881fe632be20 R08: 
 R09: 00a9
  May 26 06:19:38 server06 kernel: [75831.949952] R10: 0001 R11: 
 R12: 881fd83a7cc8
  May 26 06:19:38 server06 kernel: [75831.950961] R13: 880fe6787d40 R14: 
880fe5d95780 R15: 0080
  May 26 06:19:38 server06 kernel: [75831.951985] FS: 7fc938145700() 
GS:880fffa8() knlGS:
  May 26 06:19:38 server06 kernel: [75831.976736] CS: 0010 DS:  ES:  
CR0: 80050033
  May 26 06:19:38 server06 kernel: [75832.005183] CR2: 7fc373620930 CR3: 
000fe63fe000 CR4: 000407e0
  May 26 06:19:38 server06 kernel: [75832.033473] Stack:
  May 26 06:19:38 server06 kernel: [75832.060551] 0001 
881fe632bdb0 8109a780 881fe632bdd0
  May 26 06:19:38 server06 kernel: [75832.117385] 810d7ad6 
0001 81f1ea20 881fe632be78
  May 26 06:19:38 server06 kernel: [75832.173599] 810d983d 
881fe632be48 88a9 0001
  May 26 06:19:38 server06 kernel: [75832.231813] Call Trace:
  May 26 06:19:38 server06 kernel: [75832.258781] [8109a780] ? 
wake_up_state+0x10/0x20
  May 26 06:19:38 server06 kernel: [75832.286702] [810d7ad6] ?

[Kernel-packages] [Bug 1323165] Re: [HP ProLiant DL380p Gen8] kernel BUG at /build/buildd/linux-3.13.0/mm/memory.c:3756!

2014-06-06 Thread Philipp Kern

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 “linux” package in Ubuntu:
  Confirmed

Bug description:
  The machine becomes non-responsive, unable to ssh, high load average, trying 
to access the running java process does not work as per syslog:
  May 26 06:19:38 server06 kernel: [75831.929529] [ cut here 
]
  May 26 06:19:38 server06 kernel: [75831.930191] kernel BUG at 
/build/buildd/linux-3.13.0/mm/memory.c:3756!
  May 26 06:19:38 server06 kernel: [75831.931129] invalid opcode:  [#1] SMP
  May 26 06:19:38 server06 kernel: [75831.931729] Modules linked in: 
xt_multiport ip6t_REJECT xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 
ipt_REJECT xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables gpio_ich 
nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat 
nf_conntrack_ftp nf_conntrack iptable_filter ip_tables x_tables intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul 
glue_helper ablk_helper cryptd serio_raw sb_edac edac_core lpc_ich hpwdt hpilo 
ioatdma lp dca ipmi_si parport acpi_power_meter mac_hid tg3 ptp psmouse hpsa 
pps_core
  May 26 06:19:38 server06 kernel: [75831.941585] CPU: 4 PID: 2930 Comm: java 
Not tainted 3.13.0-24-generic #47-Ubuntu
  May 26 06:19:38 server06 kernel: [75831.942633] Hardware name: HP ProLiant 
DL380p Gen8, BIOS P70 02/10/2014
  May 26 06:19:38 server06 kernel: [75831.943583] task: 881fe8372fe0 ti: 
881fe632a000 task.ti: 881fe632a000
  May 26 06:19:38 server06 kernel: [75831.944654] RIP: 
0010:[81179051] [81179051] handle_mm_fault+0xe61/0xf10
  May 26 06:19:38 server06 kernel: [75831.946137] RSP: :881fe632bd98 
EFLAGS: 00010246
  May 26 06:19:38 server06 kernel: [75831.946885] RAX: 0100 RBX: 
7fc37320a370 RCX: 881fe632bb18
  May 26 06:19:38 server06 kernel: [75831.947902] RDX: 881fe8372fe0 RSI: 
 RDI: 800100c009e6
  May 26 06:19:38 server06 kernel: [75831.948932] RBP: 881fe632be20 R08: 
 R09: 00a9
  May 26 06:19:38 server06 kernel: [75831.949952] R10: 0001 R11: 
 R12: 881fd83a7cc8
  May 26 06:19:38 server06 kernel: [75831.950961] R13: 880fe6787d40 R14: 
880fe5d95780 R15: 0080
  May 26 06:19:38 server06 kernel: [75831.951985] FS: 7fc938145700() 
GS:880fffa8() knlGS:
  May 26 06:19:38 server06 kernel: [75831.976736] CS: 0010 DS:  ES:  
CR0: 80050033
  May 26 06:19:38 server06 kernel: [75832.005183] CR2: 7fc373620930 CR3: 
000fe63fe000 CR4: 000407e0
  May 26 06:19:38 server06 kernel: [75832.033473] Stack:
  May 26 06:19:38 server06 kernel: [75832.060551] 0001 
881fe632bdb0 8109a780 881fe632bdd0
  May 26 06:19:38 server06 kernel: [75832.117385] 810d7ad6 
0001 81f1ea20 881fe632be78
  May 26 06:19:38 server06 kernel: [75832.173599] 810d983d 
881fe632be48 88a9 0001
  May 26 06:19:38 server06 kernel: [75832.231813] Call Trace:
  May 26 06:19:38 server06 kernel: [75832.258781] [8109a780] ? 
wake_up_state+0x10/0x20
  May 26 06:19:38 server06 kernel: [75832.286702] [810d7ad6] ? 
wake_futex+0x66/0x90
  May 26 06:19:38 server06 kernel: [75832.311849] [810d983d] ? 
futex_wake_op+0x4ed/0x620
  May 26 06:19:38 server06 kernel: [75832.337329] [81721a24] 
__do_page_fault+0x184/0x560
  May 26 06:19:38 server06 kernel: [75832.363061] [82fc] ? 
acct_account_cputime+0x1c/0x20
  May 26 06:19:38 server06 kernel: [75832.387739] [8109d76b] ? 
account_user_time+0x8b/0xa0
  May 26 06:19:38 server06 kernel: [75832.411608] [8109dd84] ? 
vtime_account_user+0x54/0x60
  May 26 06:19:38 server06 kernel: [75832.436126] [81721e1a] 
do_page_fault+0x1a/0x70
  May 26 06:19:38 server06 kernel: [75832.458239] [8171e288] 
page_fault+0x28/0x30
  May 26 06:19:38 server06 kernel: [75832.481780] Code: ff 48 89 d9 4c 89 e2 4c 
89 ee 4c 89 f7 44 89 4d c8 e8 34 c1 ff ff 85 c0 0f 85 94 f5 ff ff 49 8b 3c 24 
44 8b 4d c8 e9 68 f3 ff ff 0f 0b be 8e 00 00 00 48 c7 c7 18 25 a6 81 44 89 4d 
c8 e8 18 e7
  May 26 06:19:38 server06 kernel: [75832.551672] RIP [81179051] 
handle_mm_fault+0xe61/0xf10
  May 26 06:19:38 server06 kernel: [75832.574254] RSP 881fe632bd98
  May 26 06:19:38 server06 kernel: [75832.630392] ---[ end trace 
e41b58adf8e0d72b ]---

  With Precise, it runs with 16 threads with no problem so it would
  appear a regression.

  WORKAROUND:  Run the task

[Kernel-packages] [Bug 1300739] Re: keepalived doesn't load any ipv6 virtual servers

2014-06-06 Thread Philipp Kern

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. Loadbalancing  High-Avaibility:
  New
Status in “keepalived” package in Ubuntu:
  Invalid
Status in “linux” package in Ubuntu:
  Fix Committed
Status in “keepalived” source package in Trusty:
  New
Status in “linux” source package in Trusty:
  Fix Committed
Status in “keepalived” source package in Utopic:
  Invalid
Status in “linux” source package in Utopic:
  Fix Committed

Bug description:
  SRU Justification:
  Impact: Keepalived is no longer able to load any IPv6 virtual servers for 
load balancing purposes.
  Fix: Re-enable CONFIG_IP_VS_IPV6=y
  Testcase: Attempt to load ipv6 virtual servers.


  _

  
  I've upgraded from 12.04 to 14.04 and the keepalived no longer loads any IPv6 
virtual servers.

  I get the following message when trying to list a virtual service:
  ipvsadm -L -t [2001::::xxx]:xxx
  Resource temporarily unavailable

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: keepalived 1:1.2.7-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  Date: Tue Apr  1 13:45:51 2014
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SourcePackage: keepalived
  UpgradeStatus: Upgraded to trusty on 2014-03-31 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/keepalived/+bug/1300739/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1323165] Re: [HP ProLiant DL380p Gen8] kernel BUG at /build/buildd/linux-3.13.0/mm/memory.c:3756!

2014-06-03 Thread Philipp Kern

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 Gen8] kernel BUG at
  /build/buildd/linux-3.13.0/mm/memory.c:3756!

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  The machine becomes non-responsive, unable to ssh, high load average, trying 
to access the running java process does not work as per syslog:
  May 26 06:19:38 server06 kernel: [75831.929529] [ cut here 
]
  May 26 06:19:38 server06 kernel: [75831.930191] kernel BUG at 
/build/buildd/linux-3.13.0/mm/memory.c:3756!
  May 26 06:19:38 server06 kernel: [75831.931129] invalid opcode:  [#1] SMP
  May 26 06:19:38 server06 kernel: [75831.931729] Modules linked in: 
xt_multiport ip6t_REJECT xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 
ipt_REJECT xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables gpio_ich 
nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat 
nf_conntrack_ftp nf_conntrack iptable_filter ip_tables x_tables intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul 
glue_helper ablk_helper cryptd serio_raw sb_edac edac_core lpc_ich hpwdt hpilo 
ioatdma lp dca ipmi_si parport acpi_power_meter mac_hid tg3 ptp psmouse hpsa 
pps_core
  May 26 06:19:38 server06 kernel: [75831.941585] CPU: 4 PID: 2930 Comm: java 
Not tainted 3.13.0-24-generic #47-Ubuntu
  May 26 06:19:38 server06 kernel: [75831.942633] Hardware name: HP ProLiant 
DL380p Gen8, BIOS P70 02/10/2014
  May 26 06:19:38 server06 kernel: [75831.943583] task: 881fe8372fe0 ti: 
881fe632a000 task.ti: 881fe632a000
  May 26 06:19:38 server06 kernel: [75831.944654] RIP: 
0010:[81179051] [81179051] handle_mm_fault+0xe61/0xf10
  May 26 06:19:38 server06 kernel: [75831.946137] RSP: :881fe632bd98 
EFLAGS: 00010246
  May 26 06:19:38 server06 kernel: [75831.946885] RAX: 0100 RBX: 
7fc37320a370 RCX: 881fe632bb18
  May 26 06:19:38 server06 kernel: [75831.947902] RDX: 881fe8372fe0 RSI: 
 RDI: 800100c009e6
  May 26 06:19:38 server06 kernel: [75831.948932] RBP: 881fe632be20 R08: 
 R09: 00a9
  May 26 06:19:38 server06 kernel: [75831.949952] R10: 0001 R11: 
 R12: 881fd83a7cc8
  May 26 06:19:38 server06 kernel: [75831.950961] R13: 880fe6787d40 R14: 
880fe5d95780 R15: 0080
  May 26 06:19:38 server06 kernel: [75831.951985] FS: 7fc938145700() 
GS:880fffa8() knlGS:
  May 26 06:19:38 server06 kernel: [75831.976736] CS: 0010 DS:  ES:  
CR0: 80050033
  May 26 06:19:38 server06 kernel: [75832.005183] CR2: 7fc373620930 CR3: 
000fe63fe000 CR4: 000407e0
  May 26 06:19:38 server06 kernel: [75832.033473] Stack:
  May 26 06:19:38 server06 kernel: [75832.060551] 0001 
881fe632bdb0 8109a780 881fe632bdd0
  May 26 06:19:38 server06 kernel: [75832.117385] 810d7ad6 
0001 81f1ea20 881fe632be78
  May 26 06:19:38 server06 kernel: [75832.173599] 810d983d 
881fe632be48 88a9 0001
  May 26 06:19:38 server06 kernel: [75832.231813] Call Trace:
  May 26 06:19:38 server06 kernel: [75832.258781] [8109a780] ? 
wake_up_state+0x10/0x20
  May 26 06:19:38 server06 kernel: [75832.286702] [810d7ad6] ? 
wake_futex+0x66/0x90
  May 26 06:19:38 server06 kernel: [75832.311849] [810d983d] ? 
futex_wake_op+0x4ed/0x620
  May 26 06:19:38 server06 kernel: [75832.337329] [81721a24] 
__do_page_fault+0x184/0x560
  May 26 06:19:38 server06 kernel: [75832.363061] [82fc] ? 
acct_account_cputime+0x1c/0x20
  May 26 06:19:38 server06 kernel: [75832.387739] [8109d76b] ? 
account_user_time+0x8b/0xa0
  May 26 06:19:38 server06 kernel: [75832.411608] [8109dd84] ? 
vtime_account_user+0x54/0x60
  May 26 06:19:38 server06 kernel: [75832.436126] [81721e1a] 
do_page_fault+0x1a/0x70
  May 26 06:19:38 server06 kernel: [75832.458239] [8171e288] 
page_fault+0x28/0x30
  May 26 06:19:38 server06 kernel: [75832.481780] Code: ff 48 89 d9 4c 89 e2 4c 
89 ee 4c 89 f7 44 89 4d c8 e8 34 c1 ff ff 85 c0 0f 85 94 f5 ff ff 49 8b 3c 24 
44 8b 4d c8 e9 68 f3 ff ff 0f 0b be 8e 00 00 00 48 c7 c7 18 25 a6 81 44 89 4d 
c8 e8 18 e7
  May 26 06:19:38 server06 kernel: [75832.551672] RIP [81179051] 
handle_mm_fault+0xe61/0xf10
  May 26 06:19:38 server06 kernel: [75832.574254] RSP 881fe632bd98
  May 26 06:19:38 server06 kernel: [75832.630392] ---[ end trace 
e41b58adf8e0d72b ]---

  With Precise, it runs with 16 threads

[Kernel-packages] [Bug 1302605] Re: Calls to /libx32/ld-linux-x32.so.2 hang when using auditd

2014-06-02 Thread Philipp Kern

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 added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3917

-- 
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/1302605

Title:
  Calls to /libx32/ld-linux-x32.so.2 hang when using auditd

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux” source package in Trusty:
  New

Bug description:
  I'm running trusty on a bunch of machines, doing frequent dist-
  upgrades.  My hosts have gcc-multilib installed.

  Yesterday, I noticed that initramfs generation was hanging.  Today I
  investigated further and found out that what was hanging were the
  calls to /libx32/ld-linux-x32.so.2.

  This is triggered in initramfs generation because there are at some
  hooks that incorrectly use copy_exec to copy shell scripts into the
  initramfs image.  In a working machine, when ldd encounters a shell
  script, it will first call the 64bit linker and since it fails, it
  will then call the 32bit linker which will also fail.

  However, in a machine affected by this bug, the second call will hang
  forever, preventing new image generation, and package updates in
  general, when this happens as a trigger for update-initramfs.

  Originally I thought this was related to the kernel version, since I
  was unable to reproduce in a freshly installed machine running -22 and
  was reproducing it in a machine running -20, but now I'm also
  reproducing it in a machine running -22, so it must be something else.

  I'm sorry I can't provide the exact cause right now, but I think it's
  worth noting that in some situation there might be a problem, and try
  to find out which those situations are.

  I now have one host running 3.13.0-22-generic, with
  libc6-x32=2.19-0ubuntu3, where doing ldd /usr/bin/ldd hangs, and
  another host, with the exact same kernel and libc6-x32 version where
  doing ldd /usr/bin/ldd produces the expected error message (not a
  dynamic executable).  The main difference is that the first one was
  installed yesterday and the second one was installed today.  Both are
  dist-upgraded to the latest version of everything.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1302605/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1323165] Re: [HP ProLiant DL380p Gen8] kernel BUG at /build/buildd/linux-3.13.0/mm/memory.c:3756!

2014-06-02 Thread Philipp Kern

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 stable@, but that apparently
got dropped when the patch was put into tip. This is *not* part of 3.15
yet. Instead it's currently staged for the next merge window.

** Tags removed: needs-upstream-testing
** Tags added: kernel-bug-exists-upstream

** 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/1323165

Title:
  [HP ProLiant DL380p Gen8] kernel BUG at
  /build/buildd/linux-3.13.0/mm/memory.c:3756!

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  The machine becomes non-responsive, unable to ssh, high load average, trying 
to access the running java process does not work as per syslog:
  May 26 06:19:38 server06 kernel: [75831.929529] [ cut here 
]
  May 26 06:19:38 server06 kernel: [75831.930191] kernel BUG at 
/build/buildd/linux-3.13.0/mm/memory.c:3756!
  May 26 06:19:38 server06 kernel: [75831.931129] invalid opcode:  [#1] SMP
  May 26 06:19:38 server06 kernel: [75831.931729] Modules linked in: 
xt_multiport ip6t_REJECT xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 
ipt_REJECT xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables gpio_ich 
nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat 
nf_conntrack_ftp nf_conntrack iptable_filter ip_tables x_tables intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul 
glue_helper ablk_helper cryptd serio_raw sb_edac edac_core lpc_ich hpwdt hpilo 
ioatdma lp dca ipmi_si parport acpi_power_meter mac_hid tg3 ptp psmouse hpsa 
pps_core
  May 26 06:19:38 server06 kernel: [75831.941585] CPU: 4 PID: 2930 Comm: java 
Not tainted 3.13.0-24-generic #47-Ubuntu
  May 26 06:19:38 server06 kernel: [75831.942633] Hardware name: HP ProLiant 
DL380p Gen8, BIOS P70 02/10/2014
  May 26 06:19:38 server06 kernel: [75831.943583] task: 881fe8372fe0 ti: 
881fe632a000 task.ti: 881fe632a000
  May 26 06:19:38 server06 kernel: [75831.944654] RIP: 
0010:[81179051] [81179051] handle_mm_fault+0xe61/0xf10
  May 26 06:19:38 server06 kernel: [75831.946137] RSP: :881fe632bd98 
EFLAGS: 00010246
  May 26 06:19:38 server06 kernel: [75831.946885] RAX: 0100 RBX: 
7fc37320a370 RCX: 881fe632bb18
  May 26 06:19:38 server06 kernel: [75831.947902] RDX: 881fe8372fe0 RSI: 
 RDI: 800100c009e6
  May 26 06:19:38 server06 kernel: [75831.948932] RBP: 881fe632be20 R08: 
 R09: 00a9
  May 26 06:19:38 server06 kernel: [75831.949952] R10: 0001 R11: 
 R12: 881fd83a7cc8
  May 26 06:19:38 server06 kernel: [75831.950961] R13: 880fe6787d40 R14: 
880fe5d95780 R15: 0080
  May 26 06:19:38 server06 kernel: [75831.951985] FS: 7fc938145700() 
GS:880fffa8() knlGS:
  May 26 06:19:38 server06 kernel: [75831.976736] CS: 0010 DS:  ES:  
CR0: 80050033
  May 26 06:19:38 server06 kernel: [75832.005183] CR2: 7fc373620930 CR3: 
000fe63fe000 CR4: 000407e0
  May 26 06:19:38 server06 kernel: [75832.033473] Stack:
  May 26 06:19:38 server06 kernel: [75832.060551] 0001 
881fe632bdb0 8109a780 881fe632bdd0
  May 26 06:19:38 server06 kernel: [75832.117385] 810d7ad6 
0001 81f1ea20 881fe632be78
  May 26 06:19:38 server06 kernel: [75832.173599] 810d983d 
881fe632be48 88a9 0001
  May 26 06:19:38 server06 kernel: [75832.231813] Call Trace:
  May 26 06:19:38 server06 kernel: [75832.258781] [8109a780] ? 
wake_up_state+0x10/0x20
  May 26 06:19:38 server06 kernel: [75832.286702] [810d7ad6] ? 
wake_futex+0x66/0x90
  May 26 06:19:38 server06 kernel: [75832.311849] [810d983d] ? 
futex_wake_op+0x4ed/0x620
  May 26 06:19:38 server06 kernel: [75832.337329] [81721a24] 
__do_page_fault+0x184/0x560
  May 26 06:19:38 server06 kernel: [75832.363061] [82fc] ? 
acct_account_cputime+0x1c/0x20
  May 26 06:19:38 server06 kernel: [75832.387739] [8109d76b] ? 
account_user_time+0x8b/0xa0
  May 26 06:19:38 server06 kernel: [75832.411608] [8109dd84] ? 
vtime_account_user+0x54/0x60
  May 26 06:19:38 server06 kernel: [75832.436126] [81721e1a] 
do_page_fault+0x1a/0x70
  May 26 06:19:38 server06 kernel: [75832.458239] [8171e288] 
page_fault+0x28/0x30
  May 26 06:19:38 server06 kernel:

[Kernel-packages] [Bug 1300739] Re: keepalived doesn't load any ipv6 virtual servers

2014-05-28 Thread Philipp Kern

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 ipvs even if keepalived is not in use.

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: keepalived (Ubuntu)
   Status: Confirmed = Invalid

-- 
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. Loadbalancing  High-Avaibility:
  New
Status in “keepalived” package in Ubuntu:
  Invalid
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I've upgraded from 12.04 to 14.04 and the keepalived no longer loads
  any IPv6 virtual servers.

  I get the following message when trying to list a virtual service:
  ipvsadm -L -t [2001::::xxx]:xxx
  Resource temporarily unavailable

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: keepalived 1:1.2.7-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  Date: Tue Apr  1 13:45:51 2014
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SourcePackage: keepalived
  UpgradeStatus: Upgraded to trusty on 2014-03-31 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/keepalived/+bug/1300739/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1300739] Re: keepalived doesn't load any ipv6 virtual servers

2014-05-28 Thread Philipp Kern

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 subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1300739

Title:
  keepalived doesn't load any ipv6 virtual servers

Status in Keepalived. Loadbalancing  High-Avaibility:
  New
Status in “keepalived” package in Ubuntu:
  Invalid
Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I've upgraded from 12.04 to 14.04 and the keepalived no longer loads
  any IPv6 virtual servers.

  I get the following message when trying to list a virtual service:
  ipvsadm -L -t [2001::::xxx]:xxx
  Resource temporarily unavailable

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: keepalived 1:1.2.7-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  Date: Tue Apr  1 13:45:51 2014
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SourcePackage: keepalived
  UpgradeStatus: Upgraded to trusty on 2014-03-31 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/keepalived/+bug/1300739/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1302605] Re: Calls to /libx32/ld-linux-x32.so.2 hang when using auditd

2014-05-26 Thread Philipp Kern

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 later. So this test kernel does not fix the issue.

-- 
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/1302605

Title:
  Calls to /libx32/ld-linux-x32.so.2 hang when using auditd

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux” source package in Trusty:
  New

Bug description:
  I'm running trusty on a bunch of machines, doing frequent dist-
  upgrades.  My hosts have gcc-multilib installed.

  Yesterday, I noticed that initramfs generation was hanging.  Today I
  investigated further and found out that what was hanging were the
  calls to /libx32/ld-linux-x32.so.2.

  This is triggered in initramfs generation because there are at some
  hooks that incorrectly use copy_exec to copy shell scripts into the
  initramfs image.  In a working machine, when ldd encounters a shell
  script, it will first call the 64bit linker and since it fails, it
  will then call the 32bit linker which will also fail.

  However, in a machine affected by this bug, the second call will hang
  forever, preventing new image generation, and package updates in
  general, when this happens as a trigger for update-initramfs.

  Originally I thought this was related to the kernel version, since I
  was unable to reproduce in a freshly installed machine running -22 and
  was reproducing it in a machine running -20, but now I'm also
  reproducing it in a machine running -22, so it must be something else.

  I'm sorry I can't provide the exact cause right now, but I think it's
  worth noting that in some situation there might be a problem, and try
  to find out which those situations are.

  I now have one host running 3.13.0-22-generic, with
  libc6-x32=2.19-0ubuntu3, where doing ldd /usr/bin/ldd hangs, and
  another host, with the exact same kernel and libc6-x32 version where
  doing ldd /usr/bin/ldd produces the expected error message (not a
  dynamic executable).  The main difference is that the first one was
  installed yesterday and the second one was installed today.  Both are
  dist-upgraded to the latest version of everything.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1302605/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1302605] Re: Calls to /libx32/ld-linux-x32.so.2 hang when using auditd

2014-05-26 Thread Philipp Kern

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 this time. IS_IA32 is defined like this:

#elif defined CONFIG_IA32_EMULATION
# define IS_IA32is_compat_task()

process_64.c says this about is_compat_task():

/* is_compat_task() uses the presence of the x32
   syscall bit flag to determine compat status */

And indeed:

static inline bool is_compat_task(void) 
{
return is_ia32_task() || is_x32_task();
}

** Patch added: ptrace.diff
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1302605/+attachment/4120171/+files/ptrace.diff

-- 
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/1302605

Title:
  Calls to /libx32/ld-linux-x32.so.2 hang when using auditd

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux” source package in Trusty:
  New

Bug description:
  I'm running trusty on a bunch of machines, doing frequent dist-
  upgrades.  My hosts have gcc-multilib installed.

  Yesterday, I noticed that initramfs generation was hanging.  Today I
  investigated further and found out that what was hanging were the
  calls to /libx32/ld-linux-x32.so.2.

  This is triggered in initramfs generation because there are at some
  hooks that incorrectly use copy_exec to copy shell scripts into the
  initramfs image.  In a working machine, when ldd encounters a shell
  script, it will first call the 64bit linker and since it fails, it
  will then call the 32bit linker which will also fail.

  However, in a machine affected by this bug, the second call will hang
  forever, preventing new image generation, and package updates in
  general, when this happens as a trigger for update-initramfs.

  Originally I thought this was related to the kernel version, since I
  was unable to reproduce in a freshly installed machine running -22 and
  was reproducing it in a machine running -20, but now I'm also
  reproducing it in a machine running -22, so it must be something else.

  I'm sorry I can't provide the exact cause right now, but I think it's
  worth noting that in some situation there might be a problem, and try
  to find out which those situations are.

  I now have one host running 3.13.0-22-generic, with
  libc6-x32=2.19-0ubuntu3, where doing ldd /usr/bin/ldd hangs, and
  another host, with the exact same kernel and libc6-x32 version where
  doing ldd /usr/bin/ldd produces the expected error message (not a
  dynamic executable).  The main difference is that the first one was
  installed yesterday and the second one was installed today.  Both are
  dist-upgraded to the latest version of everything.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1302605/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1221995] Re: Bluetooth Dongle (Cambridge Silicon Radio, Ltd) doesnt work on ubuntu 13.10

2014-03-20 Thread Philipp Kern

** 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 work on ubuntu
  13.10

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth device stopped working after upgrading ubuntu to 13.10.

  ~$ lsusb:
   Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)

  ~$ hciconfig
  hci0: Type: BR/EDR  Bus: USB
BD Address: 00:1B:10:00:0F:46  ACL MTU: 1017:8  SCO MTU: 64:0
DOWN 
RX bytes:457 acl:0 sco:0 events:16 errors:0
TX bytes:68 acl:0 sco:0 commands:16 errors:0
  ~$ hcitool dev
  Devices:

  device simply doesnt appear on bluetooth manager. blueman UI is
  broken.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-4-generic 3.11.0-4.9
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jorge  1954 F pulseaudio
   /dev/snd/controlC0:  jorge  1954 F pulseaudio
  Date: Fri Sep  6 22:32:45 2013
  HibernationDevice: RESUME=UUID=707ce71f-40a6-4fc3-b0a1-d24329b1c781
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: MEGAWARE MW-H61M-2H
  MarkForUpload: True
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic 
root=UUID=3480d68a-ee68-452e-b349-a2398ce3da52 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-4-generic N/A
   linux-backports-modules-3.11.0-4-generic  N/A
   linux-firmware1.113
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to saucy on 2013-08-23 (15 days ago)
  dmi.bios.date: 08/28/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5 MW
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MW-H61M-2H
  dmi.board.vendor: MEGAWARE
  dmi.board.version: v1.3 - 17/07/2012 - MWX
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEGAWARE
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5MW:bd08/28/2012:svnMEGAWARE:pnMW-H61M-2H:pvrv1.3-17/07/2012-MWX:rvnMEGAWARE:rnMW-H61M-2H:rvrv1.3-17/07/2012-MWX:cvnMEGAWARE:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MW-H61M-2H
  dmi.product.version: v1.3 - 17/07/2012 - MWX
  dmi.sys.vendor: MEGAWARE

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1221995/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1259570] Re: kexec should get a disabling sysctl

2014-02-24 Thread Philipp Kern

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 bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1259570

Title:
  kexec should get a disabling sysctl

Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux-lts-saucy” package in Ubuntu:
  Invalid
Status in “linux” source package in Precise:
  Won't Fix
Status in “linux-lts-saucy” source package in Precise:
  Fix Committed
Status in “linux” source package in Quantal:
  Won't Fix
Status in “linux-lts-saucy” source package in Quantal:
  Invalid
Status in “linux” source package in Raring:
  Invalid
Status in “linux-lts-saucy” source package in Raring:
  Invalid
Status in “linux” source package in Saucy:
  Fix Committed
Status in “linux-lts-saucy” source package in Saucy:
  Invalid
Status in “linux” source package in Trusty:
  Fix Released
Status in “linux-lts-saucy” source package in Trusty:
  Invalid

Bug description:
  To enable kexec makes sense for a generic distro kernel. But if your
  users have root in their virtual machines, 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 kexec[1]. Kees Cook wrote
  up a patch[2] that we'd like to see applied to the Ubuntu kernel to
  avoid recompilation of the distro kernel.

  I'm marking this as a security issue on the ground that it's quite
  surprising that setting kernel.modules_disabled=1 as a hardening
  feature can be subverted by using kexec.

  [1] http://mjg59.dreamwidth.org/28746.html
  [2] https://lkml.org/lkml/2013/12/9/765

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259570/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1244627] Re: Please enable CONFIG_IMA in the ubuntu kernel

2014-01-27 Thread Philipp Kern

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 kernel and its backported version.

-- 
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 CONFIG_IMA in the ubuntu kernel

Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux” source package in Saucy:
  Opinion
Status in “linux” source package in Trusty:
  Fix Released

Bug description:
  I would be doubly happy if this also went into the raring backport
  kernel.

  I chatted with apw and kees on #ubuntu-kernel earlier in the week.
  From a security engineer on our team:

  so I was mistaken. if CONFIG_IMA=y, the default policy is NULL unless
  you boot with ima_tcb=on. without ima_tcb=y, nothing is measured,
  nothing is audited, no performance/memory hit is incurred.

  Same is true for CONFIG_IMA_APPRAISE, except with the
  ima_appraise_tcb=on commandline parameter. ima appraise gives us the
  ability to sign binaries at installation time and check the signature
  at runtime.

  So we are asking that you enable CONFIG_IMA, but to not enable it via
  the kernel command line options. IMA would boot with an empty policy
  and should incur no overhead. Enterprising folks who want to run IMA
  can enable it in grub at their option.

  CONFIG_IMA=y

  and possibly:

  CONFIG_IMA_MEASURE_PCR_IDX=10
  CONFIG_IMA_AUDIT=y
  CONFIG_IMA_LSM_RULES=y

  -A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1244627/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1244627] Re: Please enable CONFIG_IMA in the ubuntu kernel

2014-01-27 Thread Philipp Kern

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 CONFIG_IMA in the ubuntu kernel

Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux” source package in Saucy:
  Opinion
Status in “linux” source package in Trusty:
  Fix Released

Bug description:
  I would be doubly happy if this also went into the raring backport
  kernel.

  I chatted with apw and kees on #ubuntu-kernel earlier in the week.
  From a security engineer on our team:

  so I was mistaken. if CONFIG_IMA=y, the default policy is NULL unless
  you boot with ima_tcb=on. without ima_tcb=y, nothing is measured,
  nothing is audited, no performance/memory hit is incurred.

  Same is true for CONFIG_IMA_APPRAISE, except with the
  ima_appraise_tcb=on commandline parameter. ima appraise gives us the
  ability to sign binaries at installation time and check the signature
  at runtime.

  So we are asking that you enable CONFIG_IMA, but to not enable it via
  the kernel command line options. IMA would boot with an empty policy
  and should incur no overhead. Enterprising folks who want to run IMA
  can enable it in grub at their option.

  CONFIG_IMA=y

  and possibly:

  CONFIG_IMA_MEASURE_PCR_IDX=10
  CONFIG_IMA_AUDIT=y
  CONFIG_IMA_LSM_RULES=y

  -A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1244627/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1244627] Re: Please enable CONFIG_IMA in the ubuntu kernel

2014-01-17 Thread Philipp Kern

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 is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1244627

Title:
  Please enable CONFIG_IMA in the ubuntu kernel

Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux” source package in Saucy:
  Triaged
Status in “linux” source package in Trusty:
  Fix Released

Bug description:
  I would be doubly happy if this also went into the raring backport
  kernel.

  I chatted with apw and kees on #ubuntu-kernel earlier in the week.
  From a security engineer on our team:

  so I was mistaken. if CONFIG_IMA=y, the default policy is NULL unless
  you boot with ima_tcb=on. without ima_tcb=y, nothing is measured,
  nothing is audited, no performance/memory hit is incurred.

  Same is true for CONFIG_IMA_APPRAISE, except with the
  ima_appraise_tcb=on commandline parameter. ima appraise gives us the
  ability to sign binaries at installation time and check the signature
  at runtime.

  So we are asking that you enable CONFIG_IMA, but to not enable it via
  the kernel command line options. IMA would boot with an empty policy
  and should incur no overhead. Enterprising folks who want to run IMA
  can enable it in grub at their option.

  CONFIG_IMA=y

  and possibly:

  CONFIG_IMA_MEASURE_PCR_IDX=10
  CONFIG_IMA_AUDIT=y
  CONFIG_IMA_LSM_RULES=y

  -A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1244627/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1259570] [NEW] kexec should get a disabling sysctl

2013-12-10 Thread Philipp Kern

*** 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 kexec[1]. Kees Cook wrote up a patch[2] that we'd like to see
applied to the Ubuntu kernel to avoid recompilation of the distro
kernel.

I'm marking this as a security issue on the ground that it's quite
surprising that setting kernel.modules_disabled=1 as a hardening feature
can be subverted by using kexec.

[1] http://mjg59.dreamwidth.org/28746.html
[2] https://lkml.org/lkml/2013/12/9/765

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

** Information type changed from Private Security 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/1259570

Title:
  kexec should get a disabling sysctl

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  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 kexec[1]. Kees Cook wrote up a patch[2] that we'd like to
  see applied to the Ubuntu kernel to avoid recompilation of the distro
  kernel.

  I'm marking this as a security issue on the ground that it's quite
  surprising that setting kernel.modules_disabled=1 as a hardening
  feature can be subverted by using kexec.

  [1] http://mjg59.dreamwidth.org/28746.html
  [2] https://lkml.org/lkml/2013/12/9/765

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259570/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1642709] Re: linux-firmware on Trusty is missing i915 binaries

[Kernel-packages] [Bug 994931] Re: Altering use_tempaddr drops all IPv6 addresses

[Kernel-packages] [Bug 994931] Re: Altering use_tempaddr drops all IPv6 addresses

[Kernel-packages] [Bug 994931] Re: Altering use_tempaddr drops all IPv6 addresses

[Kernel-packages] [Bug 1582864] Re: use after free of BOS in usb_reset_and_verify_device

[Kernel-packages] [Bug 1475662] Re: Kernel postrm calls /etc/kernel/postinst.d/*

[Kernel-packages] [Bug 1475662] [NEW] Kernel postrm calls /etc/kernel/postinst.d/*

[Kernel-packages] [Bug 1450442] Re: Kernel Oops - unable to handle kernel NULL pointer dereference at (null); Call Trace: [ffffffff810fb39b] ? audit_compare_dname_path+0x2b/0xa0

[Kernel-packages] [Bug 1398465] Re: Memory allocation failure, presumably in FUSE

[Kernel-packages] [Bug 1396065] [NEW] GPF in lru_put_end called from nfsd_cache_lookup

[Kernel-packages] [Bug 1371316] Re: Please cherry-pick an aufs patch to unbreak it in conjunction with IMA

[Kernel-packages] [Bug 1371316] Re: Please cherry-pick an aufs patch to unbreak it in conjunction with IMA

[Kernel-packages] [Bug 1368444] Re: Add support for ForcePads found on HP EliteBook Folio 1040

[Kernel-packages] [Bug 1371316] Re: Please cherry-pick an aufs patch to unbreak it in conjunction with IMA

[Kernel-packages] [Bug 1371316] [NEW] Please cherry-pick an aufs patch to unbreak it in conjunction with IMA

[Kernel-packages] [Bug 1300739] Re: keepalived doesn't load any ipv6 virtual servers

[Kernel-packages] [Bug 1302605] Re: Calls to /libx32/ld-linux-x32.so.2 hang when using auditd

[Kernel-packages] [Bug 1300739] Re: keepalived doesn't load any ipv6 virtual servers

[Kernel-packages] [Bug 1300739] Re: keepalived doesn't load any ipv6 virtual servers

[Kernel-packages] [Bug 1323165] Re: [HP ProLiant DL380p Gen8] kernel BUG at /build/buildd/linux-3.13.0/mm/memory.c:3756!

[Kernel-packages] [Bug 1323165] Re: [HP ProLiant DL380p Gen8] kernel BUG at /build/buildd/linux-3.13.0/mm/memory.c:3756!

[Kernel-packages] [Bug 1300739] Re: keepalived doesn't load any ipv6 virtual servers

[Kernel-packages] [Bug 1323165] Re: [HP ProLiant DL380p Gen8] kernel BUG at /build/buildd/linux-3.13.0/mm/memory.c:3756!

[Kernel-packages] [Bug 1302605] Re: Calls to /libx32/ld-linux-x32.so.2 hang when using auditd

[Kernel-packages] [Bug 1323165] Re: [HP ProLiant DL380p Gen8] kernel BUG at /build/buildd/linux-3.13.0/mm/memory.c:3756!

[Kernel-packages] [Bug 1300739] Re: keepalived doesn't load any ipv6 virtual servers

[Kernel-packages] [Bug 1300739] Re: keepalived doesn't load any ipv6 virtual servers

[Kernel-packages] [Bug 1302605] Re: Calls to /libx32/ld-linux-x32.so.2 hang when using auditd

[Kernel-packages] [Bug 1302605] Re: Calls to /libx32/ld-linux-x32.so.2 hang when using auditd

[Kernel-packages] [Bug 1221995] Re: Bluetooth Dongle (Cambridge Silicon Radio, Ltd) doesnt work on ubuntu 13.10

[Kernel-packages] [Bug 1259570] Re: kexec should get a disabling sysctl

[Kernel-packages] [Bug 1244627] Re: Please enable CONFIG_IMA in the ubuntu kernel

[Kernel-packages] [Bug 1244627] Re: Please enable CONFIG_IMA in the ubuntu kernel

[Kernel-packages] [Bug 1244627] Re: Please enable CONFIG_IMA in the ubuntu kernel

[Kernel-packages] [Bug 1259570] [NEW] kexec should get a disabling sysctl

35 matches

Site Navigation

Mail list logo

Footer information