回复: Fix potential overflow risks from wcscpy and sprintf

From: Yan Haibo <haibo(dot)yan(at)hotmail(dot)com>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: 回复: Fix potential overflow risks from wcscpy and sprintf
Date: 2025-06-16 18:04:09
Message-ID: CH3PR08MB861019E84B876D94AEA0FA67FA70A@CH3PR08MB8610.namprd08.prod.outlook.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thank you. Peter. It seems the patch may have been lost during our earlier communication, so I’ve reattached it here.
I hope it comes through correctly this time.
Best regards,
Haibo

________________________________
发件人: Peter Eisentraut <peter(at)eisentraut(dot)org>
发送时间: 2025年6月11日 00:43
收件人: Yan Haibo <haibo(dot)yan(at)hotmail(dot)com>; pgsql-hackers(at)lists(dot)postgresql(dot)org <pgsql-hackers(at)lists(dot)postgresql(dot)org>
主题: Re: Fix potential overflow risks from wcscpy and sprintf

On 06.06.25 22:50, Yan Haibo wrote:
> This change stems from a recent static code analysis, which identified a
> minor potential overflow issue. I would appreciate it if someone could
> review the fix at their convenience.

Please provide more detail in each case what the issue is and how you
are proposing to fix it.

Note that PostgreSQL code is regularly run through various static
analysis tools, so if the issue were super-obvious, it would probably
have been noticed by now.

Attachment Content-Type Size
0001-Mitigate-potential-overflow-risks-from-wcscpy-and-sp.patch application/octet-stream 2.9 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-06-16 18:28:06 Re: 回复: Fix potential overflow risks from wcscpy and sprintf
Previous Message Yan Haibo 2025-06-16 18:03:20 回复: Fix potential overflow risks from wcscpy and sprintf