Linux DTrace development list
 help / color / mirror / Atom feed
From: Nick Alcock <nick.alcock@oracle.com>
To: Kris Van Hees via DTrace-devel <dtrace-devel@oss.oracle.com>
Cc: dtrace@lists.linux.dev, Kris Van Hees <kris.van.hees@oracle.com>
Subject: Re: [DTrace-devel] [PATCH] test/triggers: ensure bogus-ioctl has a reasonable fd limit
Date: Wed, 31 Jul 2024 16:12:58 +0100	[thread overview]
Message-ID: <87cymtoarp.fsf@esperi.org.uk> (raw)
In-Reply-To: <SN7PR10MB6287EE29B21318FADD0A8DD1C2B12@SN7PR10MB6287.namprd10.prod.outlook.com> (Kris Van Hees via DTrace-devel's message of "Wed, 31 Jul 2024 11:03:30 -0400")

On 31 Jul 2024, Kris Van Hees via DTrace-devel spake thusly:

> The bogus-ioctl trigger has a loop to close all possible fds, and it
> was limit by rlim_max.  On some systems, that was such a high limit
> that the loop was taking too long, causing tests to time out.  Set
> the limit to 1024, so that the loop will end in reasonable time.

Boggle. I guess this has grown a lot with time :)

> Signed-off-by: Kris Van Hees <kris.van.hees@oracle.com>

Signed-off-by: Nick Alcock <nick.alcock@oracle.com>

(in practice, probably closing the first three would work almost all the
time. I can't imagine any shell weird enough to leave a thousand fds
open on entry!)

-- 
NULL && (void)

  reply	other threads:[~2024-07-31 15:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-31 15:03 [PATCH] test/triggers: ensure bogus-ioctl has a reasonable fd limit Kris Van Hees
2024-07-31 15:12 ` Nick Alcock [this message]
2024-07-31 15:19   ` [DTrace-devel] " Nick Alcock

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=87cymtoarp.fsf@esperi.org.uk \
    --to=nick.alcock@oracle.com \
    --cc=dtrace-devel@oss.oracle.com \
    --cc=dtrace@lists.linux.dev \
    --cc=kris.van.hees@oracle.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