Received-SPF: pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
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
Message-Id: <165115689135.440993.1403044617589707642.b4-ty@mit.edu>
In-Reply-To: <20220421173148.20193-1-lczerner@redhat.com>
References: <20220421173148.20193-1-lczerner@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

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>