Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vQUEM-008ngx-0x for pgpool-general@arkaria.postgresql.org; Tue, 02 Dec 2025 17:32:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vQUEL-009Gbd-0r for pgpool-general@arkaria.postgresql.org; Tue, 02 Dec 2025 17:32:01 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vQUEL-009GbW-07 for pgpool-general@lists.postgresql.org; Tue, 02 Dec 2025 17:32:01 +0000 Received: from mail-wm1-x32d.google.com ([2a00:1450:4864:20::32d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vQUEH-002mhY-1o for pgpool-general@lists.postgresql.org; Tue, 02 Dec 2025 17:32:00 +0000 Received: by mail-wm1-x32d.google.com with SMTP id 5b1f17b1804b1-4779a637712so36323355e9.1 for ; Tue, 02 Dec 2025 09:31:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1764696717; x=1765301517; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=nXdwOzlEBiTC+/F6J2guTj+89TI6Hfq2yOhNYYvwJDg=; b=lazUrUhCSv+HvztK/yUJUtnzev1xCaXi/3qMOlz7ldGrgkAX039MKyiiKQtlyl1waY UrOJqoadkuSm2OI37rE0DlnHMpJDe+oNP2ySAsjMKBxMpBjkzu1aGnuNgVYEkPbCqTDL 2A1FcWTNky9nEJqKiHmxc1oM78UtfNb4P7VBYTlSR9j8jU0QijCSZH8+6scDsN+2675t ACV87ssn7TExrimLw54O7iuyUnt96PgFjkDIvT69Zn3qR4vKfugTyNMYW34+KnExKmAp WqoTUnfyn4GWZN1hD2sN93SpFvAajH3Ibqd3uEeU55tXOFY8TM0KA1Bs71RCsTK2NxHm QdRw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1764696717; x=1765301517; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-gg:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=nXdwOzlEBiTC+/F6J2guTj+89TI6Hfq2yOhNYYvwJDg=; b=R3KePm/ls8KYjNI6jXBsbl28tHRRNF+kYKHnAWwU9vh96os3RarTJ8/k6FtfX4BgWN DmpznUVPeDLFDf3OoUrp2TtdSZukQjKvFNdhJx9sGT/40Lg/+S8j86tEoWF27cXCFVDJ ZbctNtSDOiB1zV2A8fJTE2WAxmy7qEMc1WedT7CdEeyI82OMRJ6VpKolLdhqNTybaXAT EqCmDq7Hs8gHooyqTuUpLYEIu9IpPC1wT+NmVL8webPrN0Q0Yvpl6m0EFJkrifBElVyi 7mUE/A7kf7Wfq6j2VIvAZ/iYLwDlBRkAOcySXp3M2qlEK5IWaxXP8LAWoaUrKFnDgX7H HGlQ== X-Gm-Message-State: AOJu0YzjqnYjoVTJQPUhA3vzU3HV0EE3epKN2O+z9ecWydXmkbchfl5O fOlM3JA4AOnWBhWrHy80E5VQ87CPxcq4ID5BoSvD8Lb+lUno6EkGDwa/jpRfpjNCHFohVSA8c6e D7JQJ2Jk/cm6OSVd5vdp2IXo/cRhIBvicO9/r X-Gm-Gg: ASbGncsAtc0H/ea/HKiQDuR5MF2llrYK3GwcOUMH1KwGNf13+iZx3gOBXcO6qkLdjxl rGWScY1RsxwRIDkntt0pI1zZ2NiNI9JdYKLb6iMh6pxTFEtb3OkYdzOrivvdwR+K5MAt5p1VL34 r6u+7ZA2TDMfTzqckWXePTJIVr05BMYDJuCqQu7q2Ksz5zk0wXDK0HchR8DeJinS77Wt77kQ4d0 2mI9QJRHWGoWcu5EtDxI0yJnwjegXaqAnwb0VzJoqo1gmbn+2CIEeDM3Lb+BpLwYhFYulAxJ6Eq GtPi1rE= X-Google-Smtp-Source: AGHT+IFidf4OgDahJ0U3FNfVPOECFa1r25yLL3Lj0eayQ5dO1QJD/vfOlzr9EHcYVDjL8W9uibPCfXxLx2QwXS+dPI8= X-Received: by 2002:a5d:5850:0:b0:42b:3252:14c5 with SMTP id ffacd0b85a97d-42cc1cf3b19mr44553813f8f.28.1764696716735; Tue, 02 Dec 2025 09:31:56 -0800 (PST) MIME-Version: 1.0 References: <20251130.102712.131456481338876013.ishii@postgresql.org> <20251202.140205.427777414210613577.ishii@postgresql.org> In-Reply-To: <20251202.140205.427777414210613577.ishii@postgresql.org> From: zam bak Date: Tue, 2 Dec 2025 12:31:46 -0500 X-Gm-Features: AWmQ_bnrKfbVxhyD_usVsB3-oLxucsuCdHtaNoRsLOe_SNPQroF1Xu2iC3h9YmM Message-ID: Subject: Re: "buffer overflow detected" when running SHOW POOL_STATUS To: Tatsuo Ishii Cc: pgpool-general@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, Dec 2, 2025 at 12:02=E2=80=AFAM Tatsuo Ishii = wrote: > > >> Unfortunately, I was not able to reproduce the issue on my Ubuntu 24 > >> and Rocky Linux 10.1 box (pgpool is compiled from source code). > >> So there are some questions: > >> > >> - Is the issue occurred even when you execute other pgpool command? > >> (for example "show pool_processes") > > > > No. Only getting this issue when running SHOW POOL_STATUS > > I found a bug with SHOW POOL_STATUS (and pcp_pool_status). The bug > broke the data segment used for the conversion from binary form of > backend flag (in this case ALWAYS_PRIMARY. Other flag does not raise > the issue) to string representation, which caused the buffer overflow > issue. > > Attached is the patch to fix the issue. Ishii-san Thank you for finding the bug and fixing it... I think this bug warrants a new patch release or a rebuild so we can use the latest 4.6 in production... Is it possible to release a new RPM build 4.6.4-2 or 4.6.5? Regards Z.... > > Best regards, > -- > Tatsuo Ishii > SRA OSS K.K. > English: http://www.sraoss.co.jp/index_en/ > Japanese:http://www.sraoss.co.jp >