From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8818EC433F5 for ; Sun, 20 Feb 2022 14:51:16 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243997AbiBTOvg (ORCPT ); Sun, 20 Feb 2022 09:51:36 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:58968 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238761AbiBTOvf (ORCPT ); Sun, 20 Feb 2022 09:51:35 -0500 Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5765245AD8 for ; Sun, 20 Feb 2022 06:51:14 -0800 (PST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id E86065C0217; Sun, 20 Feb 2022 09:51:11 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Sun, 20 Feb 2022 09:51:11 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h=cc :cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm3; bh=bBxaZJZsbLlIZtiGi04Ze1DarzKjcjNhKFT69q QvhPo=; b=G+2P6ZfX8hW8cuPSncGazABSS+U9N0y2Cj4/FUYa7wyWd4jbBmhlRJ w0WGhN3VFJYuK2/k8BHLAS9er8KRb10m9Ezvi3UtnVDGMtFoOQmUHUYUmxfFe51/ qxiR6vdqoEUWWOU0sMofl14qOC3IHQcT0s4j9OklebBAKhVnpILRs/tkcCuXeslb Fjkla3DiooQsRFomqx5mao7nUrZN9dbNOViEUp3EnIyI7xiLKG11ffIPuuwm8Sr/ sLgbVwDfvZXsn0bS1YCEwhAEXPyrIDx2mGhIoOFtqvllWUCS7iFaS1IjNfaozm0l iiEohWIbe4VbJpBC/zoeAivnZ/+Tm5sg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=bBxaZJZsbLlIZtiGi 04Ze1DarzKjcjNhKFT69qQvhPo=; b=cfjah0NEsgFkYX1tbTP6fJd95ZtjFl7X3 NFAELFTE2cBhOqzbbCOaVoq85pdsoHUhV7NVYQwzCInyJxVP0EXYrQrGVfJN8SDa utBq1SKkcGxulSSdRsqjYcIGrK8UowAv/Ke401FpgDUI0lioBWZh66TAlKj2fQwu MnZf5oz88kwIXyYzubLyinZGSNbpbtIiMoWuD87EZ4dlTE1dnh4V/CnolwilwAZd hdCRbHARdipzT/MYxMmpiuke+Px2+oqWqlyXrfCXv1k0av8DqYBJ9ZCzJGp9US8w J3bV6O+WcwJW3LfaxAEg4q8b7XW+ZQdYtpt2d7iCwDVV3RM8i2zGA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrkeeggdejudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvuffkfhggtggujgesthdtredttddtvdenucfhrhhomhepifhrvghgucfm jfcuoehgrhgvgheskhhrohgrhhdrtghomheqnecuggftrfgrthhtvghrnhepveeuheejgf ffgfeivddukedvkedtleelleeghfeljeeiueeggeevueduudekvdetnecuvehluhhsthgv rhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepghhrvghgsehkrhhorghhrd gtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 20 Feb 2022 09:51:10 -0500 (EST) Date: Sun, 20 Feb 2022 15:51:08 +0100 From: Greg KH To: Theodore Ts'o Cc: Leah Rumancik , stable@vger.kernel.org, Zhang Yi Subject: Re: [PATCH for 5.4 1/3] ext4: check for out-of-order index extents in ext4_valid_extent_entries() Message-ID: References: <20220217225914.40363-1-leah.rumancik@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Fri, Feb 18, 2022 at 02:57:22PM -0500, Theodore Ts'o wrote: > Leah, thanks for doing the backport to 5.4! And Greg, thanks for queuing them up. > > I note that if we first cherry pick into 4.19.y a fix from 5.2 that > probably should have been cc'ed to stable to begin with: > > 0a944e8a6c66 ("ext4: don't perform block validity checks on the journal inode") This commit is already in the following releases: 3.16.85 4.4.221 4.4.263 4.9.221 4.9.263 4.14.178 4.14.227 4.19.73 4.19.182 5.2 5.7.18 5.8.4 > Leah's three backports to 5.4 will then apply to 4.19 LTS; I've run > regression tests with the cherry-pick of 0a944e8a6c66 and Leah's three > backports applied to 4.19.230, and the resulting kernel looks fine and > prevents a kernel crash when running ext4/054. > > Greg, would you prefer that I send the patches for 4.19.y, or do you > have what you need to do the cherry pick (all of the cherry picks are > clean, and didn't require any manual resolution)? The second commit does not apply cleanly, so I would need working backported ones to get this right. I have queued up the first one now already. thanks, greg k-h