Re: Memory leakage in libpq valgrind test - Mailing list pgsql-bugs

From Sudheer H R
Subject Re: Memory leakage in libpq valgrind test
Date
Msg-id 0545B0F7-A685-447B-B6C9-FA843EDE367C@tekenlight.com
Whole thread Raw
In response to Re: Memory leakage in libpq valgrind test  (Michael Paquier <michael@paquier.xyz>)
List pgsql-bugs
OK….

I am looking for links where I can raise an issue with libgssapi_krb5 team.
Would any of you know an appropriate link to raise the issue.

I am doing the test on ubuntu linux and on aarch64 (ARM 64)

Sudheer


> On 01-Mar-2023, at 12:29 PM, Michael Paquier <michael@paquier.xyz> wrote:
>
> On Wed, Mar 01, 2023 at 01:43:50AM -0500, Tom Lane wrote:
>> So ... why do you think this is our bug, and not a Kerberos bug?
>> The leak seems to be buried quite far in libgssapi_krb5.so.
>
> Yeah, libpq calls gss_acquire_cred().  So, assuming that the leak is
> localized within one of the resources allocated by this call, there is
> nothing in the kerberos docs that point to a routine to free it:
> https://web.mit.edu/kerberos/krb5-latest/doc/appdev/gssapi.html or
> gssapi.rst in its code tree.
>
> I may be missing something, of course.
> --
> Michael




pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Memory leakage in libpq valgrind test
Next
From: Julien Rouhaud
Date:
Subject: Re: BUG #17812: LOCK TABLE IN ACCESS EXCLUSIVE MODE with a view returns an empty tuple set