From: "Theodore Ts'o" <tytso@mit.edu>
To: linux-ext4@vger.kernel.org, Lukas Czerner <lczerner@redhat.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>, Nils Bars <nils_bars@t-online.de>
Subject: Re: [PATCH] e2fsprogs: add sanity check to extent manipulation
Date: Thu, 28 Apr 2022 10:43:40 -0400 [thread overview]
Message-ID: <165115689135.440993.1403044617589707642.b4-ty@mit.edu> (raw)
In-Reply-To: <20220421173148.20193-1-lczerner@redhat.com>
On Thu, 21 Apr 2022 19:31:48 +0200, Lukas Czerner wrote:
> It is possible to have a corrupted extent tree in such a way that a leaf
> node contains zero extents in it. Currently if that happens and we try
> to traverse the tree we can end up accessing wrong data, or possibly
> even uninitialized memory. Make sure we don't do that.
>
> Additionally make sure that we have a sane number of bytes passed to
> memmove() in ext2fs_extent_delete().
>
> [...]
Applied, thanks!
[1/1] libext2fs: add sanity check to extent manipulation
commit: ab51d587bb9b229b1fade1afd02e1574c1ba5c76
Best regards,
--
Theodore Ts'o <tytso@mit.edu>
prev parent reply other threads:[~2022-04-28 14:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 17:31 [PATCH] e2fsprogs: add sanity check to extent manipulation Lukas Czerner
2022-04-28 14:43 ` Theodore Ts'o [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=165115689135.440993.1403044617589707642.b4-ty@mit.edu \
--to=tytso@mit.edu \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=nils_bars@t-online.de \
/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 NNTP newsgroup(s).