public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/29117] New: debuginfod client leaking fd's for cache misses
Date: Tue, 03 May 2022 23:45:01 +0000	[thread overview]
Message-ID: <bug-29117-10460@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=29117

            Bug ID: 29117
           Summary: debuginfod client leaking fd's for cache misses
           Product: elfutils
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: debuginfod
          Assignee: unassigned at sourceware dot org
          Reporter: fche at redhat dot com
                CC: elfutils-devel at sourceware dot org
  Target Milestone: ---

There appears to be an fd leak in the debuginfod client cache-miss code path. 
This can exhaust fd resources over time, which is bad for a long-lived client
such as debuginfod itself.  Trying to reproduce the trigger operation sequence.
 But the end result is the client holding onto file descriptors like 

debuginfo 10215 debuginfod   81r   REG                8,0         0   927302
/var/cache/debuginfod/.debuginfod_client_cache/3b47e7f26e7ed1dda18165fb20cb56769affdd19/debuginfo
(deleted)

... while the files actually exist, despite the (deleted) tag; maybe they were
recreated later:

[root@elastic ~]# ls -ald
/var/cache/debuginfod/.debuginfod_client_cache/3b47e7f26e7ed1dda18165fb20cb56769affdd19/debuginfo
-rw-r--r-- 1 debuginfod debuginfod 0 May  3 23:40
/var/cache/debuginfod/.debuginfod_client_cache/3b47e7f26e7ed1dda18165fb20cb56769affdd19/debuginfo

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2022-05-03 23:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-03 23:45 fche at redhat dot com [this message]
2022-05-04  1:59 ` [Bug debuginfod/29117] " fche at redhat dot com
2022-05-04 11:08 ` mark at klomp dot org
2022-05-04 11:09 ` mark at klomp dot org
2022-05-04 14:48 ` fche at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-29117-10460@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=elfutils-devel@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).