From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id 6143C3858D32 for ; Mon, 27 Feb 2023 16:47:37 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 6143C3858D32 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1677516457; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=rUv2QbT04BLXjNc85QRmLFWB9Rzx5jKHT06wPjfrxns=; b=itv4ZN84BqKCf+Mz4SHtnPmIN/kXpWBxMODYdeDlbsO+3yQmaXGOG4D8jY2xeU5yIWeUoL Pua5dP1SNe9DNvgPJIbIpcJBV2Yo85M1cLAdNc7Y3NSB1I4fU3N2aIPcXD1wU49kaR0kq2 QYS4NyqNu5ccLMfjWKmbQJ1q4pyTov4= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-86-Na8oPgS6P_KIRVqUAYPxhQ-1; Mon, 27 Feb 2023 11:47:35 -0500 X-MC-Unique: Na8oPgS6P_KIRVqUAYPxhQ-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.rdu2.redhat.com [10.11.54.1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 2C4E62A59579; Mon, 27 Feb 2023 16:47:35 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.45.226.66]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 549D6404BEC5; Mon, 27 Feb 2023 16:47:34 +0000 (UTC) From: Florian Weimer To: Gioele Barabucci Cc: Gioele Barabucci via Systemtap Subject: Re: [PATCH] dtrace: Use deterministic temp file creation for all temp files References: <6bfff40c-2c4b-c119-116d-7834310299d7@svario.it> <87fsarm7m5.fsf@oldenburg.str.redhat.com> <3de411c4-8cbd-667b-a64e-aeeac297ea94@svario.it> Date: Mon, 27 Feb 2023 17:47:26 +0100 In-Reply-To: <3de411c4-8cbd-667b-a64e-aeeac297ea94@svario.it> (Gioele Barabucci's message of "Mon, 27 Feb 2023 16:59:58 +0100") Message-ID: <87356rm4wx.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.1 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-4.9 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: * Gioele Barabucci: >> It might be more robust to use a dedicated temporary directory and a >> predictable file name under that directory. > > Doesn't this suffer from the same issue? If dtrace finds that > predictable dir/file path it will exit (impeding a second run). Or am > I missing something? The idea is to use a predictable file name in a temporary directory with an unpredictable name (created using mkdtemp or one of the higher-level facilities). Thanks, Florian