From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <SRS0=T/K7=5G=redhat.com=fweimer@sourceware.org>
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124])
	by sourceware.org (Postfix) with ESMTPS id E1F423858D1E
	for <libc-help@sourceware.org>; Mon,  9 Jan 2023 17:11:49 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org E1F423858D1E
Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com
Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;
	s=mimecast20190719; t=1673284309;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 in-reply-to:in-reply-to:references:references;
	bh=WK0xZ7izVc5Srk79umB/kGBtps+c2uIUsNKWdFpYhLA=;
	b=YnOfBL8TLN0WZqZ1+P6cmX3HZw0jyYZz1qPaeZZMREsappYG973k6PthhG9vKKnd2Xowkb
	3S5ZZtxgLB3KBwSf3I3ToiJlPEOItCedpWtvY+YV5dfmRjvf+2KnmmYFfNCiktSLYCFfxl
	KA59H953ZRAaLQKlqqu2DQDkLJ3p3MA=
Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com
 [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS
 (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
 us-mta-215-u3lEWxfUMX6RobovWnUOcg-1; Mon, 09 Jan 2023 12:11:46 -0500
X-MC-Unique: u3lEWxfUMX6RobovWnUOcg-1
Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.rdu2.redhat.com [10.11.54.8])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 02CD2382C967;
	Mon,  9 Jan 2023 17:11:46 +0000 (UTC)
Received: from oldenburg.str.redhat.com (unknown [10.2.16.32])
	by smtp.corp.redhat.com (Postfix) with ESMTPS id 29866C16027;
	Mon,  9 Jan 2023 17:11:44 +0000 (UTC)
From: Florian Weimer <fweimer@redhat.com>
To: Parthiban <parthiban@linumiz.com>
Cc: libc-help@sourceware.org
Subject: Re: glibc mq_notify memory leak report
References: <abe21391-8d9f-4035-f0a5-d4f8a1a7d83f@linumiz.com>
Date: Mon, 09 Jan 2023 18:11:43 +0100
In-Reply-To: <abe21391-8d9f-4035-f0a5-d4f8a1a7d83f@linumiz.com>
	(parthiban@linumiz.com's message of "Mon, 9 Jan 2023 20:43:13 +0530")
Message-ID: <87wn5viqeo.fsf@oldenburg.str.redhat.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux)
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 3.1 on 10.11.54.8
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain
X-Spam-Status: No, score=-4.9 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org
List-Id: <libc-help.sourceware.org>

* > Dear All,
>
> I have the following code snippet and `mq_close`, `mq_unlink` is
> called in exit path.  But with valgrind, I have the summary about
> possibly lost.
>
> How to gracefully remove the notification during exit path?

I think this is the same issue that was reported here for timer_create
(which also has a helper thread):

  libc timer_create with option SIGEV_THREAD system call having memory
  leaks after timer_delete system call
  <https://sourceware.org/bugzilla/show_bug.cgi?id=29705>

I don't think there is a good way to fix this.  It's not an unbounded
leak, so it does not impact the application while it runs.

Thanks,
Florian