From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 5B41C43A37; Thu, 1 Feb 2024 12:04:14 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 23226402A7; Thu, 1 Feb 2024 12:04:14 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id C33BF40299 for ; Thu, 1 Feb 2024 12:04:12 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1706785452; 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=b0Ei6TXxAisIGJj5K1227jM63TOyPIsjlo5LYw35RDE=; b=SOE1cNWe2P/oV97PTcQPEKtAVumVTF359kuYmA7QZ+/lG8VmmbgwjBgm9ad6Z2AWlAhWOd aRQuL+AV4r+NTuT3OtdZ+VFQqiBV0pF6WfBtGGK4kmoVV/MWZBnV/l0vWg2IciiuDTwCGQ POGiB/5JWOQo31oRZfpPF/zKguvxvYQ= Received: from mail-lj1-f200.google.com (mail-lj1-f200.google.com [209.85.208.200]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-635-QM9S8wvrO_iQEPerXAVfNA-1; Thu, 01 Feb 2024 06:04:11 -0500 X-MC-Unique: QM9S8wvrO_iQEPerXAVfNA-1 Received: by mail-lj1-f200.google.com with SMTP id 38308e7fff4ca-2d07cf08cc8so2583881fa.2 for ; Thu, 01 Feb 2024 03:04:11 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1706785449; x=1707390249; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=b0Ei6TXxAisIGJj5K1227jM63TOyPIsjlo5LYw35RDE=; b=RW3bGpW0eHI/KpcX9u3hHc6Yr5wNCBQG4G2dx1Vj8w0rbduPeaObBUPHe2uCkGmZY3 i2O1J0NFi9QWCLNqkRsOZCKko3vBGno4fNWIrtceIcyl8DJKtEoyJVa6D2305FTvKgFP WoUezUGay62XiZwvWia5wQDAjrhLMcZNTLA7yAazgbe7alj9BPFaOvq3ibu8VVJ11OYW MpykBklLKp48/qqOuoStil5D+fX/290EdZJStsqeOPGMu7fCGOoraotOQ7ODb7uz+HDk AEVbqCXFO6MRswp/gwWUqKqm8d+yCeL7gYQYxSbAOf23h7bAjRS5OB7dXPJiYygobq7D 0W+A== X-Gm-Message-State: AOJu0Yy8QH5krv1t1zYicR0zzsvs0IGoHyr0LlmXpfKxgjMUK8Qgw7A2 //SunPkfZKmGQ4yN3oYh20EwKqeY0kEIYT+hNwB6y1l0a6bztUhjszOuX7yR/dunFs/iV6J9H0m VfrKHXcreb1+sMLxev4UiYAygkt7k0IUhst2A+pbBW18P25FWL9qpaOUU2xT2cXjgZuH5A6CV0X HRYIhFUKmtv2nDf3k= X-Received: by 2002:a2e:9dcf:0:b0:2cd:ea12:fd8e with SMTP id x15-20020a2e9dcf000000b002cdea12fd8emr2843426ljj.50.1706785449693; Thu, 01 Feb 2024 03:04:09 -0800 (PST) X-Google-Smtp-Source: AGHT+IFsqjICALMNjamWaEG3NsYLiKVq17PrF7Vx7kr7CDph5fm7sEcSa5J8f/Ey5/Po1DN5swfSUAPAGK9BCULUr78= X-Received: by 2002:a2e:9dcf:0:b0:2cd:ea12:fd8e with SMTP id x15-20020a2e9dcf000000b002cdea12fd8emr2843411ljj.50.1706785449402; Thu, 01 Feb 2024 03:04:09 -0800 (PST) MIME-Version: 1.0 References: <20231114082539.1858594-1-huangdengdui@huawei.com> <20231114161648.1a575ab6@hermes.local> In-Reply-To: <20231114161648.1a575ab6@hermes.local> From: David Marchand Date: Thu, 1 Feb 2024 12:03:57 +0100 Message-ID: Subject: Re: [PATCH 00/43] replace strerror To: Stephen Hemminger , Dengdui Huang Cc: dev@dpdk.org, ferruh.yigit@amd.com, lihuisong@huawei.com, fengchengwen@huawei.com, liuyonglong@huawei.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On Wed, Nov 15, 2023 at 1:17=E2=80=AFAM Stephen Hemminger wrote: > > On Tue, 14 Nov 2023 16:24:56 +0800 > Dengdui Huang wrote: > > > The function strerror() is insecure in a multi-thread environment. > > This series of patches fix it. In this patchset, only the libs and > > drivers are modified. > > Doing such a global replace seems like a lot of changes for many > cases that are not multi-threaded. > Is there an actual fix mixed somewhere in this series? If so, it should be clearly identified for backports. --=20 David Marchand