From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>,
Hongjie Fang <hongjiefang@asrmicro.com>,
tytso@mit.edu, jaegeuk@kernel.org, ebiggers@kernel.org
Cc: linux-fscrypt@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH V3] fscrypt: don't set policy for a dead directory
Date: Fri, 10 May 2019 12:30:43 +0000 [thread overview]
Message-ID: <20190510123044.AE901217F5@mail.kernel.org> (raw)
In-Reply-To: <1557453923-5286-1-git-send-email-hongjiefang@asrmicro.com>
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 9bd8212f981e ext4 crypto: add encryption policy and password salt support.
The bot has tested the following trees: v5.0.14, v4.19.41, v4.14.117, v4.9.174, v4.4.179.
v5.0.14: Build OK!
v4.19.41: Build OK!
v4.14.117: Build OK!
v4.9.174: Failed to apply! Possible dependencies:
Unable to calculate
v4.4.179: Failed to apply! Possible dependencies:
002ced4be642 ("fscrypto: only allow setting encryption policy on directories")
0b81d0779072 ("fs crypto: move per-file encryption from f2fs tree to fs/crypto")
0cab80ee0c9e ("f2fs: fix to convert inline inode in ->setattr")
0fac2d501b0d ("f2fs crypto: fix spelling typo in comment")
0fd785eb931d ("f2fs: relocate is_merged_page")
1dafa51d45c6 ("f2fs crypto: check for too-short encrypted file names")
36b35a0dbe90 ("f2fs: support data flush in background")
55d1cdb25a81 ("f2fs: relocate tracepoint of write_checkpoint")
6b2553918d8b ("replace ->follow_link() with new method that could stay in RCU mode")
6beceb5427aa ("f2fs: introduce time and interval facility")
8dc0d6a11e7d ("f2fs: early check broken symlink length in the encrypted case")
922ec355f863 ("f2fs crypto: avoid unneeded memory allocation when {en/de}crypting symlink")
9e8925b67a80 ("locks: Allow disabling mandatory locking at compile time")
a263669fa18f ("f2fs crypto: sync with ext4's fname padding")
ae1086686487 ("f2fs crypto: handle unexpected lack of encryption keys")
b9d777b85ff1 ("f2fs: check inline_data flag at converting time")
ce855a3bd092 ("f2fs crypto: f2fs_page_crypto() doesn't need a encryption context")
d0239e1bf520 ("f2fs: detect idle time depending on user behavior")
d323d005ac4a ("f2fs: support file defragment")
dffd0cfa06d4 ("fscrypt: use ENOTDIR when setting encryption policy on nondirectory")
ed3360abbc04 ("f2fs crypto: make sure the encryption info is initialized on opendir(2)")
How should we proceed with this patch?
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-05-10 12:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 2:05 [PATCH V3] fscrypt: don't set policy for a dead directory Hongjie Fang
2019-05-10 12:30 ` Sasha Levin [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-05-22 2:02 Hongjie Fang
2019-05-29 20:50 ` Eric Biggers
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=20190510123044.AE901217F5@mail.kernel.org \
--to=sashal@kernel.org \
--cc=ebiggers@kernel.org \
--cc=hongjiefang@asrmicro.com \
--cc=jaegeuk@kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tytso@mit.edu \
/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).