From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id tOn9NTpPCWfQ+QkAWB0awg (envelope-from ) for ; Fri, 11 Oct 2024 12:15:54 -0400 Authentication-Results: simark.ca; dkim=pass (1024-bit key; unprotected) header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256 header.s=mimecast20190719 header.b=F/SrKg2s; dkim-atps=neutral Received: by simark.ca (Postfix, from userid 112) id B991A1E358; Fri, 11 Oct 2024 12:15:54 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-7.8 required=5.0 tests=ARC_SIGNED,ARC_VALID,BAYES_00, DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI, RCVD_IN_DNSWL_BLOCKED,RCVD_IN_VALIDITY_CERTIFIED,RCVD_IN_VALIDITY_RPBL, RCVD_IN_VALIDITY_SAFE autolearn=ham autolearn_force=no version=4.0.0 Received: from server2.sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 187BC1E355 for ; Fri, 11 Oct 2024 12:15:54 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 76C1E3857014 for ; Fri, 11 Oct 2024 16:15:53 +0000 (GMT) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTP id D6E023858D26 for ; Fri, 11 Oct 2024 16:15:31 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org D6E023858D26 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org D6E023858D26 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=170.10.133.124 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1728663335; cv=none; b=H24Cc2Go3gN8ZhfAIMXsuaivyMRwQ4jmUYZxPv9S/xg6h10ggXf0Gsei3y0tSq2nQAOVJ07zKD7zh+dHzTIZyAZr7kDpHm6FBqFPxrRk7LdeU7piGQGXg20kLdc/PDhNhrGkVTH5Cr3drr5ay09NE7JvBOvNiRuo1Nyl9RsnOYw= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1728663335; c=relaxed/simple; bh=2hxBQe4qQLtve0nNMG8LcLz4r4ZeDZdnbPK3Z3HQ5qw=; h=DKIM-Signature:Date:From:To:Subject:Message-ID:MIME-Version; b=YIGXw4jSaB1J+0Du8NlAyhlmWJhQbFMUOAY7Bkduv99eePfU1OQ8DBxwMtgmJXWOShFBi43I8C8DUDJnIPE9tDM1wGs4icvhb49fQ77vT+Ef+gAKf0MF5NczZd69rlEVt+1KV/V9PEbP7NKJxmVz7s+caSEeco7YBPucGxHBXQc= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1728663331; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=924qZU/FWiVtMPNhQ1kwT10gWCbVFpWrHHDI+020uAY=; b=F/SrKg2scp6cwRa/AOVGm9bB+vzbei87OOkjC2OAy/7R6zOlX3/v6+rJdA1D3LcRRZxLBz yogJRSMFGt3qbl6xNbcssi8aBMcUmcguhi1MWUnCVlVxOrNzAIXXy5ryuU/GSUKe7pnWGk +P9vzRf4Y1E1pjeyC8CGWDTcwAIy9YU= Received: from mx-prod-mc-05.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-550-zi146kC_PcusBVVg-rcJOA-1; Fri, 11 Oct 2024 12:15:30 -0400 X-MC-Unique: zi146kC_PcusBVVg-rcJOA-1 Received: from mx-prod-int-02.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-02.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.15]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-05.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 19CD41955F45; Fri, 11 Oct 2024 16:15:29 +0000 (UTC) Received: from f40-zbm-amd (unknown [10.22.64.14]) by mx-prod-int-02.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id E23A41955F42; Fri, 11 Oct 2024 16:15:27 +0000 (UTC) Date: Fri, 11 Oct 2024 09:15:22 -0700 From: Kevin Buettner To: Eli Zaretskii Cc: gdb-patches@sourceware.org Subject: Re: [PATCH 11/11] Add TLS NEWS entry and document 'set force-internal-tls-address-lookup' command Message-ID: <20241011091522.15944ade@f40-zbm-amd> In-Reply-To: <8634l319h2.fsf@gnu.org> References: <20241010022552.47637-1-kevinb@redhat.com> <20241010022552.47637-12-kevinb@redhat.com> <86iku0339g.fsf@gnu.org> <20241010162631.6fe74f4b@f40-zbm-amd> <8634l319h2.fsf@gnu.org> Organization: Red Hat MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.0 on 10.30.177.15 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: gdb-patches-bounces~public-inbox=simark.ca@sourceware.org On Fri, 11 Oct 2024 08:42:33 +0300 Eli Zaretskii wrote: > > With regard to the question of why you might want to force use of > > internal TLS lookup, it's mostly for testing purposes. > > If this is for testing, shouldn't it be a maint command? Well, _mostly_ for testing. I can imagine situations where a GDB user prints a TLS variable, but doesn't believe the answer being printed. Being able to switch the TLS address resolution mechanism allows the user to see if a different answer might be printed. That said, I'm fine with changing it, since it's likely to be used by few aside from GDB maintainers. I'll make this change for the v2 series. (I also need to address some problems found by the Linaro regression tester.) Kevin