[Bug 941968] Re: lockfile-create hangs inside lxc containers (potential buffer overflow?)

[Launchpad Bug Tracker]

This bug was fixed in the package liblockfile - 1.09-5ubuntu1

---------------
liblockfile (1.09-5ubuntu1) raring; urgency=low

  * debian/patches/fix-buffer-overflows.patch: Fix buffer overflows when
    building strings
    - Protect against overflows caused by long hostnames (LP: #941968)
    - Protect against overflows caused by large PID numbers (LP: #1011477)
 -- Tyler Hicks <tyhicks at canonical.com>   Wed, 09 Jan 2013 12:23:07 -0800

** Changed in: liblockfile (Ubuntu)
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/941968

Title:
  lockfile-create hangs inside lxc containers (potential buffer
  overflow?)

Status in “liblockfile” package in Ubuntu:
  Fix Released

Bug description:
  I've hit this problem while testing juju charms that use ntp
  (specifically hbase - bug 800708).

  The first instance in the first LXC container start OK; however
  subsequent instances in other LXC containers fail as ntp is installed:

  root      1157   416  0 14:48 ?        00:00:00 /usr/bin/dpkg --status-fd 49 --configure resolvconf:all openjdk-6-jre-headless:amd
  root      1313     1  0 14:48 ?        00:00:00 /usr/sbin/libvirtd -d
  root      1398  1157  0 14:48 ?        00:00:00 /bin/sh /var/lib/dpkg/info/ntp.postinst configure
  root      1437  1398  0 14:48 ?        00:00:00 /bin/sh /usr/sbin/invoke-rc.d ntp start
  root      1453  1437  0 14:48 ?        00:00:00 /bin/sh /etc/init.d/ntp start
  root      1458  1453  0 14:48 ?        00:00:00 lockfile-create /var/lock/ntpdate

  Running lockfile-create by hand after killing the hanging lockfile-
  create:

  ubuntu at jamespage-hendrix-hbase-regioncluster-2:~$ lockfile-create /var/lock/ntpdate
  *** glibc detected *** lockfile-create: malloc(): memory corruption (fast): 0x000000000105b0e0 ***

  [Test Case]
  Set a hostname of 64 characters (HOST_NAME_MAX is 64) and create a lock file:

  $ lock=/var/lock/lockfile-create-test
  $ lockfile-remove $lock
  $ sudo hostname hostna01234567890123456789012345678901234567890123456789
  $ lockfile-create $lock

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lxc 0.7.5-3ubuntu30
  ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
  Uname: Linux 3.2.0-17-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 1.93-0ubuntu2
  Architecture: amd64
  Date: Mon Feb 27 14:49:30 2012
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)

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