From: Dan Carpenter <dan.carpenter@linaro.org>
To: Alex Shumsky <alexthreed@gmail.com>
Cc: u-boot@lists.denx.de, "Marek Behún" <kabel@kernel.org>,
"Qu Wenruo" <wqu@suse.com>, "Tom Rini" <trini@konsulko.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] fs: btrfs: fix out of bounds write
Date: Tue, 18 Jun 2024 09:41:40 +0300 [thread overview]
Message-ID: <5898a17d-8fcf-47ae-bdb2-c647eca9997d@moroto.mountain> (raw)
In-Reply-To: <20240617194947.1928008-1-alexthreed@gmail.com>
On Mon, Jun 17, 2024 at 10:49:47PM +0300, Alex Shumsky wrote:
> Fix btrfs_read/read_and_truncate_page write out of bounds of destination
> buffer. Old behavior break bootstd malloc'd buffers of exact file size.
> Previously this OOB write have not been noticed because distroboot usually
> read files into huge static memory areas.
>
> Signed-off-by: Alex Shumsky <alexthreed@gmail.com>
Could you add a Fixes tag?
regards,
dan carpenter
next prev parent reply other threads:[~2024-06-18 6:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 19:49 [PATCH] fs: btrfs: fix out of bounds write Alex Shumsky
2024-06-17 22:22 ` Qu Wenruo
2024-06-18 6:03 ` David Disseldorp
2024-06-18 6:41 ` Dan Carpenter [this message]
2024-06-18 7:45 ` Marek Behún
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=5898a17d-8fcf-47ae-bdb2-c647eca9997d@moroto.mountain \
--to=dan.carpenter@linaro.org \
--cc=alexthreed@gmail.com \
--cc=kabel@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=wqu@suse.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