From: Christian Ebner <c.ebner@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup v3] etc: raise nofile soft limit to hard limit for proxmox-backup-proxy
Date: Thu, 20 Nov 2025 16:12:48 +0100 [thread overview]
Message-ID: <bfb9e45f-2e5a-439d-9df6-6dc783efd93d@proxmox.com> (raw)
In-Reply-To: <292443c9-8f1d-40f5-817b-1698e47c7a33@proxmox.com>
On 11/20/25 4:05 PM, Thomas Lamprecht wrote:
> Am 20.11.25 um 15:32 schrieb Christian Ebner:
>> This is acceptable since PBS does not directly depend on problematic
>> select() calls as verified via `nm` and does not use it in linked
>> libraries to the best of my knowledge.
>>
>
> Isn't above and
With above I intended to state that the PBS code itself does not call
into select(), while below are dependencies on shared objects which
might call into select() according to their symbols.
>
>> Occurrences of the symbol according to `nm -D <shared-object>` are:
>>
>> /lib/x86_64-linux-gnu/libapt-pkg.so.7.0
>> U select@GLIBC_2.2.5
>> /lib/x86_64-linux-gnu/libpam.so.0
>> U select@GLIBC_2.2.5
>> /lib/x86_64-linux-gnu/libc.so.6
>> 000000000010e140 W select@@GLIBC_2.2.5
>> /lib/x86_64-linux-gnu/libcrypto.so.3
>> U select@GLIBC_2.2.5
>
> above a contradiction? Or do I just misinterpret this?
> As it would seem to me that the usage of select symbols would in fact
> show that this might not be safe, or?
>
> If the API calls into any function of those libs, that might might then create
> a FD >= 1024 inside which then could get passed down to any of their select
> calls?
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2025-11-20 15:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 14:31 Christian Ebner
2025-11-20 15:05 ` Thomas Lamprecht
2025-11-20 15:12 ` Christian Ebner [this message]
2025-11-20 17:23 ` Thomas Lamprecht
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=bfb9e45f-2e5a-439d-9df6-6dc783efd93d@proxmox.com \
--to=c.ebner@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=t.lamprecht@proxmox.com \
/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