[Bug 1257186] Re: memory leakage messages (no talloc stackframe)

[Ryan Harper]

On Thu, Jun 25, 2015 at 7:44 PM, Chad <Chad at finkenbiner.com> wrote:

> Would someone explain the last several updates?  What is the SRU team
>
and what kind of review are they performing?  Finally (and possibly most


Hi, I think most of your questions will be answered by looking at the
Stable Release Update wiki page:

https://wiki.ubuntu.com/StableReleaseUpdates

I've applied and tested the upstream fix for this issue to the Samba
package in trusty.
I've confirmed that the fix that's upstream in Samba is not present in the
current development release (Wily)
And I've packaged up the fix for trusty and submitted for the SRU team to
review.  If approved, there will be
a test package published to be verified and if all goes well it will be
released into the
Trusty updates stream.

importantly), how can the status be "In Progress" when the ticket is
> still "Unassigned"?
>

Work is under-way, specially the Trusty SRT task is in progress; bug
assignment isn't required AFAIK.

Hope that helps,
Ryan

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1257186

Title:
  memory leakage messages (no talloc stackframe)

Status in One Hundred Papercuts:
  New
Status in Samba:
  Fix Released
Status in samba package in Ubuntu:
  Fix Released
Status in samba source package in Trusty:
  In Progress
Status in samba package in Debian:
  New

Bug description:
  [Impact]

   * Warning messages related to memory leaks "no talloc stackframe at"
     are present at login and other PAM services when libpam-smbpass is
     installed.

   * Backporting the fix resolves the warning messages and memory leak.

   * The upload incorporates the upstream fix from Samba.

  [Test Case]

   * On a Trusty 14.04 system:
     1. sudo apt-get install libpam-smbpass
     2. sudo passwd <user on the system>
     3. if bug is present in samba, then the output looks like:

  % sudo passwd <user>
  no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory
  Enter new UNIX password: 

     4. After applying the updated packages the 'no talloc stackframe at'
     message is no longer present during step 2.

  
  [Regression Potential] 

   * The changes are in the area of samba password authentication so it
  would be worth exercising Samba client password manipulation.


  [Original Description]
  This message appears a lot as of a recent update to samba (Trusty development branch):

  no talloc stackframe at ../source3/param/loadparm.c:4831, leaking
  memory

  From this upstream bug report, I am lead to believe the issue is in
  libpam-smbpass, but I don't really know for sure.

  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728666

  I am filing this bug report mainly so that I can refer to it on the
  testing tracker as an issue, while still setting the test case to
  pass. Note that other than the error message itself, I am not aware of
  any bad side effect.

  doug at v32-serv04:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:    Ubuntu Trusty Tahr (development branch)
  Release:        14.04
  Codename:       trusty

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