Linux DTrace development list
 help / color / mirror / Atom feed
From: Nick Alcock <nick.alcock@oracle.com>
To: Sam James <sam@gentoo.org>
Cc: dtrace-devel@oss.oracle.com, <dtrace@lists.linux.dev>
Subject: Re: [DTrace-devel] [PATCH] Revert "dt_pid: pid grabs should be shortlived"
Date: Thu, 19 Jun 2025 13:51:29 +0100	[thread overview]
Message-ID: <87tt4bzyge.fsf@esperi.org.uk> (raw)
In-Reply-To: <8734c2hte6.fsf@gentoo.org> (Sam James's message of "Sat, 14 Jun 2025 23:04:33 +0100")

On 14 Jun 2025, Sam James outgrape:

> Sam James via DTrace-devel <dtrace-devel@oss.oracle.com> writes:
>
>> Nick Alcock via DTrace-devel <dtrace-devel@oss.oracle.com> writes:
>>
>>> On 22 May 2025, eugene loh verbalised:
>>>
>>>> From: Eugene Loh <eugene.loh@oracle.com>
>>>>
>>>> Commit 4aec5c9931eb ("dt_pid: pid grabs should be shortlived") made
>>>> grabs short-lived.  No test cases show the utility of this patch.
>>>> Meanwhile, the patch causes roughly a dozen tests to fail on OL9
>>>> when the test suite is started remotely using ssh, closing ttys.  The
>>>
>>> I think this is a consequence of another bug (Psystem_daemon() was
>>> failing to detect that systemd was running correctly on systemd v2
>>
>> (Do you mean cgroup v2?)

Yes indeed. The heat and pollen is ruining my brain :/

$random_related_word v2

      reply	other threads:[~2025-06-19 12:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-22 18:10 [PATCH] Revert "dt_pid: pid grabs should be shortlived" eugene.loh
2025-06-13 14:23 ` Nick Alcock
2025-06-13 20:12   ` [DTrace-devel] " Sam James
2025-06-14 22:04     ` Sam James
2025-06-19 12:51       ` Nick Alcock [this message]

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