From: Luc Van Oostenryck <lucvoo@kernel.org>
To: Jeff Layton <jlayton@kernel.org>
Cc: linux-sparse@vger.kernel.org, luc.vanoostenryck@gmail.com
Subject: Re: [PATCH] linearize.c: fix potential buffer overrun
Date: Mon, 18 Dec 2023 14:56:01 +0100 [thread overview]
Message-ID: <q5nxyfe6t4mguhtxtvh7a6wbct4bctj6ynrvd3pftvmiw5rymg@fl4cprexyjhm> (raw)
In-Reply-To: <20230222155244.133890-1-jlayton@kernel.org>
On Wed, Feb 22, 2023 at 10:52:44AM -0500, Jeff Layton wrote:
> The resulting string won't be nearly 64 bytes, but "buf" is only 16
> bytes long here, and this causes FORTIFY_SOURCE to barf when given the
> right options.
>
> Signed-off-by: Jeff Layton <jlayton@kernel.org>
Pushed to mainline now. Sorry for this very long delay.
-- Luc
prev parent reply other threads:[~2023-12-18 13:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 15:52 [PATCH] linearize.c: fix potential buffer overrun Jeff Layton
2023-12-18 13:56 ` Luc Van Oostenryck [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=q5nxyfe6t4mguhtxtvh7a6wbct4bctj6ynrvd3pftvmiw5rymg@fl4cprexyjhm \
--to=lucvoo@kernel.org \
--cc=jlayton@kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).