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>,
        syzbot+15cd994e273307bf5cfa@syzkaller.appspotmail.com,
        tadeusz.struk@linaro.org
Subject: Re: [PATCH] ext4: block range must be validated before use in ext4_mb_clear_bb()
Date:   Fri, 22 Jul 2022 09:58:17 -0400
Message-Id: <165849767595.303416.2399065700843216204.b4-ty@mit.edu>
In-Reply-To: <20220714165903.58260-1-lczerner@redhat.com>
References: <20220714095300.ffij7re6l5n6ixlg@fedora> <20220714165903.58260-1-lczerner@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Thu, 14 Jul 2022 18:59:03 +0200, Lukas Czerner wrote:
> Block range to free is validated in ext4_free_blocks() using
> ext4_inode_block_valid() and then it's passed to ext4_mb_clear_bb().
> However in some situations on bigalloc file system the range might be
> adjusted after the validation in ext4_free_blocks() which can lead to
> troubles on corrupted file systems such as one found by syzkaller that
> resulted in the following BUG
> 
> [...]

Applied, thanks!

[1/1] ext4: block range must be validated before use in ext4_mb_clear_bb()
      commit: 91e204c46741b198693dd88bd7b03a5b5fe0ce17

Best regards,
-- 
Theodore Ts'o <tytso@mit.edu>