From: Markus Elfring <Markus.Elfring@web.de>
To: dm-devel@lists.linux.dev, kernel-janitors@vger.kernel.org,
Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@kernel.org>,
Mikulas Patocka <mpatocka@redhat.com>,
Ondrej Kozina <okozina@redhat.com>,
Waiman Long <longman@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 2/2] dm-crypt: Use common error handling code in crypt_set_keyring_key()
Date: Wed, 18 Sep 2024 16:10:22 +0200 [thread overview]
Message-ID: <4b4379e6-e341-46da-a951-57b31edf3997@web.de> (raw)
In-Reply-To: <68ee5a00-888c-420f-a3a9-a556c19ee6eb@web.de>
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Wed, 18 Sep 2024 15:34:45 +0200
Add a jump target so that a bit of exception handling can be better reused
at the end of this function implementation.
Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
---
drivers/md/dm-crypt.c | 24 ++++++++++++------------
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/drivers/md/dm-crypt.c b/drivers/md/dm-crypt.c
index dae2fe3cb182..3d2247cfd42b 100644
--- a/drivers/md/dm-crypt.c
+++ b/drivers/md/dm-crypt.c
@@ -2614,8 +2614,8 @@ static int crypt_set_keyring_key(struct crypt_config *cc, const char *key_string
key = request_key(type, key_desc + 1, NULL);
if (IS_ERR(key)) {
- kfree_sensitive(new_key_string);
- return PTR_ERR(key);
+ ret = PTR_ERR(key);
+ goto free_new_key_string;
}
down_read(&key->sem);
@@ -2623,23 +2623,23 @@ static int crypt_set_keyring_key(struct crypt_config *cc, const char *key_string
ret = set_key(cc, key);
up_read(&key->sem);
key_put(key);
- if (ret < 0) {
- kfree_sensitive(new_key_string);
- return ret;
- }
+ if (ret < 0)
+ goto free_new_key_string;
/* clear the flag since following operations may invalidate previously valid key */
clear_bit(DM_CRYPT_KEY_VALID, &cc->flags);
ret = crypt_setkey(cc);
+ if (ret)
+ goto free_new_key_string;
- if (!ret) {
- set_bit(DM_CRYPT_KEY_VALID, &cc->flags);
- kfree_sensitive(cc->key_string);
- cc->key_string = new_key_string;
- } else
- kfree_sensitive(new_key_string);
+ set_bit(DM_CRYPT_KEY_VALID, &cc->flags);
+ kfree_sensitive(cc->key_string);
+ cc->key_string = new_key_string;
+ return 0;
+free_new_key_string:
+ kfree_sensitive(new_key_string);
return ret;
}
--
2.46.0
next prev parent reply other threads:[~2024-09-18 14:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 14:05 [PATCH 0/2] dm-crypt: Adjustments for crypt_set_keyring_key() Markus Elfring
2024-09-18 14:08 ` [PATCH 1/2] dm-crypt: Use up_read() together with key_put() only once in crypt_set_keyring_key() Markus Elfring
2024-09-18 14:10 ` Markus Elfring [this message]
2024-09-18 16:38 ` [PATCH 2/2] dm-crypt: Use common error handling code " Mikulas Patocka
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=4b4379e6-e341-46da-a951-57b31edf3997@web.de \
--to=markus.elfring@web.de \
--cc=agk@redhat.com \
--cc=dm-devel@lists.linux.dev \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mpatocka@redhat.com \
--cc=okozina@redhat.com \
--cc=snitzer@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
Powered by JetHome