From: Sascha Hauer <s.hauer@pengutronix.de>
To: ecryptfs@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Tyler Hicks <code@tyhicks.com>,
Sascha Hauer <s.hauer@pengutronix.de>
Subject: [PATCH] ecryptfs: Fix typo in message
Date: Wed, 24 Feb 2021 12:30:59 +0100 [thread overview]
Message-ID: <20210224113059.28445-1-s.hauer@pengutronix.de> (raw)
ecryptfs_decrypt_page() issues a warning "Error encrypting extent". This
should be "Error decrypting extent" instead.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
fs/ecryptfs/crypto.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/ecryptfs/crypto.c b/fs/ecryptfs/crypto.c
index a48116aae02c..0fed4ff02f69 100644
--- a/fs/ecryptfs/crypto.c
+++ b/fs/ecryptfs/crypto.c
@@ -535,7 +535,7 @@ int ecryptfs_decrypt_page(struct page *page)
rc = crypt_extent(crypt_stat, page, page,
extent_offset, DECRYPT);
if (rc) {
- printk(KERN_ERR "%s: Error encrypting extent; "
+ printk(KERN_ERR "%s: Error decrypting extent; "
"rc = [%d]\n", __func__, rc);
goto out;
}
--
2.29.2
next reply other threads:[~2021-02-24 11:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 11:30 Sascha Hauer [this message]
2021-04-18 17:38 ` [PATCH] ecryptfs: Fix typo in message Tyler Hicks
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=20210224113059.28445-1-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=code@tyhicks.com \
--cc=ecryptfs@vger.kernel.org \
--cc=linux-kernel@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).