<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">

<html lang="en">

<head>

<meta content="text/html; charset=US-ASCII" http-equiv="Content-Type">

<title>

GitLab

</title>

<style>img {

max-width: 100%; height: auto;

}

</style>

</head>

<body>

<div class="content">

<p style="color: #777777;">

<a href="https://gitlab.com/simo5">Simo Sorce</a>

<a href="https://gitlab.com/gnutls/gnutls/-/issues/1125#note_468363715">commented</a>:

</p>

<div style="">

<p dir="auto">Looking at this initialization code I do not see it makes a lot of sense.

At any given time two threads in an application can be competing and opening file descriptors. There is no way to guarantee sequential fd number allocation, so this check should be removed.</p>

<p dir="auto">The problem is whether there is code in GnuTLS that somehow depends on sequential fd allocation, if that's the case that code needs to be changed.</p>

</div>

</div>

<div class="footer" style="margin-top: 10px;">

<p style="font-size: small; color: #666;">

—

<br>

Reply to this email directly or <a href="https://gitlab.com/gnutls/gnutls/-/issues/1125#note_468363715">view it on GitLab</a>.

<br>

You're receiving this email because of your account on gitlab.com.

If you'd like to receive fewer emails, you can

<a href="https://gitlab.com/-/sent_notifications/0e80f57cd190f8b26c2454f1a502b3b7/unsubscribe">unsubscribe</a>

from this thread or

adjust your notification settings.

<script type="application/ld+json">{"@context":"http://schema.org","@type":"EmailMessage","action":{"@type":"ViewAction","name":"View Issue","url":"https://gitlab.com/gnutls/gnutls/-/issues/1125#note_468363715"}}</script>

</p>

</div>

</body>

</html>