On Jun 9, 2016 7:43 PM, Steve Langasek <[email protected]> wrote:
>
> And what makes you so sure this is a pam bug, rather than a libasan bug (or
> a glibc bug)?

Definitely not sure. I tried various apps dlopening other libraries (both PAM 
and nonPAM) and none showed a leak, only pam_open_session().

> Compiling without -lasan and running under valgrind doesn't show any such
> leak.

I can confirm this. I had the same result (no leak) with valgrind. Did not 
check if it was a default suppression though.

>And running pamtest under 'ltrace -e dlopen+dlclose -l
> /lib/x86_64-linux-gnu/libdl.so.2' shows an equal number of calls to dlopen()
> and dlclose().
>
> So I don't see any way that this is a pam bug.

If you think it appropriate I can log it against both glibc and libasan.



MRV Communications is a global supplier of packet and optical solutions that 
power the world’s largest networks. Our products combine innovative hardware 
with intelligent software to make networks smarter, faster and more efficient.

Reply via email to