← Back to team overview

touch-packages team mailing list archive

[Bug 1109327] Update Released

 

The verification of the Stable Release Update for eglibc has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to eglibc in Ubuntu.
https://bugs.launchpad.net/bugs/1109327

Title:
  who command gets "who: memory exhausted" for certain inputs

Status in The GNU C Library:
  Fix Released
Status in eglibc package in Ubuntu:
  Fix Released
Status in eglibc source package in Lucid:
  Won't Fix
Status in eglibc source package in Precise:
  Fix Released
Status in eglibc source package in Quantal:
  Won't Fix
Status in eglibc package in Debian:
  Fix Released

Bug description:
  SRU Justification:
  [Impact] 
   * When using who, certain characters can cause issues with eglibc's vfprintf causing memory issues and who to print 'memory exhausted'.

  [Test Case]

   * Download wtmp.clean.
   * locale-gen en_US.UTF-8 # if necessary
   * LANG=en_US.UTF-8 who wtmp.clean
   * If you see 'who: memory exhausted' the test failed.

  [Regression Potential]

   * This patch reverts a change that fixes the issue in BZ #6530.
   * The patch also adds a test case to check for handling of incomplete multi-byte characters.
   * upstream patch URL: http://sourceware.org/git/?p=glibc.git;a=commit;h=715a900c9085907fa749589bf738b192b1a2bda5

  --

  * Description:
  When running who with the attached file we get an error of "who: memory exhausted".
      $ who wtmp.clean

  This works fine in newer versions of eglibc. I was able to determine that coreutils was not the problem
  by using the precise version of coreutils with the raring eglibc version. In that case the problem went away.
  In addition I've compiled the precise version for raring, and the problem is not present.

  * Versions affected:
  This affects current Lucid, Oneiric, Precise and Quantal eglibc versions.
  2.11.1-0ubuntu7.12
  2.13-20ubuntu5.3
  2.15-0ubuntu10.4
  2.15-0ubuntu20.1
  But does not affect Raring eglibc ( 2.17-0ubuntu1 )

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