Re: [PATCH 00/43] replace strerror

2024-11-06 Thread huangdengdui
On 2024/11/7 2:57, 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. > > strerror is ok in m

RE: [PATCH 00/43] replace strerror

2024-10-22 Thread Morten Brørup
> From: Stephen Hemminger [mailto:step...@networkplumber.org] > Sent: Wednesday, 15 November 2023 01.17 > > 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

Re: [PATCH 00/43] replace strerror

2024-02-01 Thread David Marchand
On Wed, Nov 15, 2023 at 1:17 AM 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. > > Doin

Re: [PATCH 00/43] replace strerror

2023-11-14 Thread Stephen Hemminger
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 ar