From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org
Cc: Florian Weimer <fw@deneb.enyo.de>
Cc: Peter Maydell <peter.maydell@linaro.org>
Cc: Andy Lutomirski <luto@kernel.org>
Cc: stable@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] ext4: Give 32bit personalities 32bit hashes
Date: Tue, 17 Mar 2020 22:30:21 +0000 [thread overview]
Message-ID: <20200317223022.9B1A420738@mail.kernel.org> (raw)
In-Reply-To: <20200317113153.7945-1-linus.walleij@linaro.org>
Hi
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all
The bot has tested the following trees: v5.5.9, v5.4.25, v4.19.109, v4.14.173, v4.9.216, v4.4.216.
v5.5.9: Build OK!
v5.4.25: Build OK!
v4.19.109: Failed to apply! Possible dependencies:
592ddec7578a ("ext4: use IS_ENCRYPTED() to check encryption status")
b886ee3e778e ("ext4: Support case-insensitive file name lookups")
v4.14.173: Failed to apply! Possible dependencies:
2ee6a576be56 ("fs, fscrypt: add an S_ENCRYPTED inode flag")
69fe2d75dd91 ("btrfs: make the delalloc block rsv per inode")
79f015f21653 ("btrfs: cleanup extent locking sequence")
8b62f87bad9c ("Btrfs: rework outstanding_extents")
ae5e165d855d ("fs: new API for handling inode->i_version")
b886ee3e778e ("ext4: Support case-insensitive file name lookups")
ee73f9a52a34 ("ext4: convert to new i_version API")
v4.9.216: Failed to apply! Possible dependencies:
39bc88e5e38e ("arm64: Disable TTBR0_EL1 during normal kernel execution")
5e9d0e3d9ea6 ("powerpc/lib: Fix randconfig build failure in sstep.c")
783d94854499 ("ext4: add EXT4_IOC_GOINGDOWN ioctl")
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")
v4.4.216: Failed to apply! Possible dependencies:
39bc88e5e38e ("arm64: Disable TTBR0_EL1 during normal kernel execution")
4dffbfc48d65 ("arm64/efi: mark UEFI reserved regions as MEMBLOCK_NOMAP")
57f4959bad0a ("arm64: kernel: Add support for User Access Override")
6c94f27ac847 ("arm64: switch to relative exception tables")
783d94854499 ("ext4: add EXT4_IOC_GOINGDOWN ioctl")
7c0f6ba682b9 ("Replace <asm/uaccess.h> with <linux/uaccess.h> globally")
7dd01aef0557 ("arm64: trap userspace "dc cvau" cache operation on errata-affected core")
9b7365fc1c82 ("ext4: add FS_IOC_FSSETXATTR/FS_IOC_FSGETXATTR interface support")
9e8e865bbe29 ("arm64: unify idmap removal")
b886ee3e778e ("ext4: Support case-insensitive file name lookups")
d5370f754875 ("arm64: prefetch: add alternative pattern for CPUs without a prefetcher")
e5bc22a42e4d ("arm64/efi: split off EFI init and runtime code for reuse by 32-bit ARM")
e7227d0e528f ("arm64: Cleanup SCTLR flags")
ee73f9a52a34 ("ext4: convert to new i_version API")
f7d924894265 ("arm64/efi: refactor EFI init and runtime code for reuse by 32-bit ARM")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
prev parent reply other threads:[~2020-03-17 22:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 11:31 [PATCH] ext4: Give 32bit personalities 32bit hashes Linus Walleij
2020-03-17 11:52 ` Florian Weimer
2020-03-17 12:38 ` Linus Walleij
2020-03-17 11:58 ` Peter Maydell
2020-03-19 15:13 ` Linus Walleij
2020-03-19 15:25 ` Peter Maydell
2020-03-19 22:23 ` Linus Walleij
2020-03-24 2:34 ` Theodore Y. Ts'o
2020-03-24 9:29 ` Peter Maydell
2020-03-24 18:47 ` Theodore Y. Ts'o
2020-03-24 21:17 ` Linus Walleij
2020-03-17 22:28 ` Andreas Dilger
2020-03-19 15:18 ` Linus Walleij
2020-03-17 22:30 ` Sasha Levin [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=20200317223022.9B1A420738@mail.kernel.org \
--to=sashal@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@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).