From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Jan Kara <jack@suse.cz>
To: Ted Tso <tytso@mit.edu>
Cc: <linux-ext4@vger.kernel.org>, Jan Kara <jack@suse.cz>
Cc: stable@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] ext4: Fix checking of entry validity
Date: Thu, 06 Aug 2020 01:24:05 +0000 [thread overview]
Message-ID: <20200806012405.E3B2122B40@mail.kernel.org> (raw)
In-Reply-To: <20200731162135.8080-1-jack@suse.cz>
Hi
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag
fixing commit: 109ba779d6cc ("ext4: check for directory entries too close to block end").
The bot has tested the following trees: v5.7.11, v5.4.54, v4.19.135, v4.14.190, v4.9.231, v4.4.231.
v5.7.11: Build OK!
v5.4.54: Build OK!
v4.19.135: Build OK!
v4.14.190: Build OK!
v4.9.231: Failed to apply! Possible dependencies:
364443cbcfe7 ("ext4: convert DAX reads to iomap infrastructure")
39bc88e5e38e ("arm64: Disable TTBR0_EL1 during normal kernel execution")
7046ae35329f ("ext4: Add iomap support for inline data")
7c0f6ba682b9 ("Replace <asm/uaccess.h> with <linux/uaccess.h> globally")
9cf09d68b89a ("arm64: xen: Enable user access before a privcmd hvc call")
b886ee3e778e ("ext4: Support case-insensitive file name lookups")
bd38967d406f ("arm64: Factor out PAN enabling/disabling into separate uaccess_* macros")
ee73f9a52a34 ("ext4: convert to new i_version API")
eeca7ea1baa9 ("ext4: use current_time() for inode timestamps")
v4.4.231: Failed to apply! Possible dependencies:
12735f881952 ("ext4: pre-zero allocated blocks for DAX IO")
2dcba4781fa3 ("ext4: get rid of EXT4_GET_BLOCKS_NO_LOCK flag")
364443cbcfe7 ("ext4: convert DAX reads to iomap infrastructure")
7046ae35329f ("ext4: Add iomap support for inline data")
705965bd6dfa ("ext4: rename and split get blocks functions")
b886ee3e778e ("ext4: Support case-insensitive file name lookups")
ba5843f51d46 ("ext4: use pre-zeroed blocks for DAX page faults")
c86d8db33a92 ("ext4: implement allocation of pre-zeroed blocks")
ee73f9a52a34 ("ext4: convert to new i_version API")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
next prev parent reply other threads:[~2020-08-06 1:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 16:21 [PATCH] ext4: Fix checking of entry validity Jan Kara
2020-08-01 23:18 ` Sasha Levin
2020-08-06 1:24 ` Sasha Levin [this message]
2020-08-07 20:07 ` tytso
2020-08-09 15:53 ` Sasha Levin
2020-08-13 16:25 ` Sasha Levin
2020-08-19 23:56 ` Sasha Levin
2020-08-26 13:53 ` Sasha Levin
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=20200806012405.E3B2122B40@mail.kernel.org \
--to=sashal@kernel.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
/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).