From: Tyler Hicks <tyhicks@canonical.com>
To: Aditya Pakki <pakki001@umn.edu>
Cc: kjlu@umn.edu, ecryptfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ecryptfs: replace BUG_ON with error handling code
Date: Fri, 14 Feb 2020 11:38:18 -0600 [thread overview]
Message-ID: <20200214173818.GB250165@elm> (raw)
In-Reply-To: <20191215172404.28204-1-pakki001@umn.edu>
On 2019-12-15 11:24:04, Aditya Pakki wrote:
> In crypt_scatterlist, if the crypt_stat argument is not set up
> correctly, we avoid crashing, by returning the error upstream.
> This patch performs the fix.
>
> Signed-off-by: Aditya Pakki <pakki001@umn.edu>
Hi Aditya - I wanted to check in to see if you are able to submit a new
revision taking into account the feedback from Markus.
Also, I'm curious if you've been able to hit this BUG_ON() or if you are
just being proactive in cleaning up this function?
Let me know if I can help you prepare a v2 of this patch. Thanks!
Tyler
> ---
> fs/ecryptfs/crypto.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/fs/ecryptfs/crypto.c b/fs/ecryptfs/crypto.c
> index f91db24bbf3b..a064b408d841 100644
> --- a/fs/ecryptfs/crypto.c
> +++ b/fs/ecryptfs/crypto.c
> @@ -311,8 +311,10 @@ static int crypt_scatterlist(struct ecryptfs_crypt_stat *crypt_stat,
> struct extent_crypt_result ecr;
> int rc = 0;
>
> - BUG_ON(!crypt_stat || !crypt_stat->tfm
> - || !(crypt_stat->flags & ECRYPTFS_STRUCT_INITIALIZED));
> + if (!crypt_stat || !crypt_stat->tfm
> + || !(crypt_stat->flags & ECRYPTFS_STRUCT_INITIALIZED))
> + return -EINVAL;
> +
> if (unlikely(ecryptfs_verbosity > 0)) {
> ecryptfs_printk(KERN_DEBUG, "Key size [%zd]; key:\n",
> crypt_stat->key_size);
> --
> 2.20.1
>
next prev parent reply other threads:[~2020-02-14 17:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-15 17:24 [PATCH] ecryptfs: replace BUG_ON with error handling code Aditya Pakki
2019-12-15 21:20 ` Markus Elfring
2020-02-14 17:38 ` Tyler Hicks [this message]
2020-02-14 18:01 ` Aditya Pakki
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=20200214173818.GB250165@elm \
--to=tyhicks@canonical.com \
--cc=ecryptfs@vger.kernel.org \
--cc=kjlu@umn.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=pakki001@umn.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