From: Eric Biggers <ebiggers@google.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, tytso@mit.edu
Subject: Re: [PATCH] fscrypto: make filename crypto functions return 0 on success
Date: Wed, 14 Sep 2016 19:54:41 -0700 [thread overview]
Message-ID: <20160915025441.GA80824@google.com> (raw)
In-Reply-To: <20160915001021.GB50095@jaegeuk>
On Wed, Sep 14, 2016 at 05:10:21PM -0700, Jaegeuk Kim wrote:
> Hi Eric,
>
> On Wed, Sep 14, 2016 at 04:00:45PM -0700, Eric Biggers wrote:
> > Several filename crypto functions: fname_decrypt(),
> > fscrypt_fname_disk_to_usr(), and fscrypt_fname_usr_to_disk(), returned
> > the output length on success or -errno on failure. However, the output
> > length was redundant with the value written to 'oname->len'. It is also
> > potentially error-prone to make callers have to check for '< 0' instead
> > of '!= 0'.
>
> At a glance, you missed some places like
> - fscrypt_fname_usr_to_disk() in ext4_symlink() and f2fs_symlink()
> - fscrypt_fname_disk_to_usr() in dx_show_leaf() and f2fs_fill_dentries()
>
Those callers don't have to be updated because they only check for an error
value --- they don't use the return value as a length. I did check all the
callers of fscrypt_fname_{usr_to_disk,disk_to_usr()}, and only the three I
update in the patch used the return value as a length.
Eric
next prev parent reply other threads:[~2016-09-15 2:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 23:00 [PATCH] fscrypto: make filename crypto functions return 0 on success Eric Biggers
2016-09-15 0:10 ` Jaegeuk Kim
2016-09-15 2:54 ` Eric Biggers [this message]
2016-09-15 16:54 ` Jaegeuk Kim
2016-09-15 17:22 ` Eric Biggers
2016-09-15 9:50 ` Andreas Dilger
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=20160915025441.GA80824@google.com \
--to=ebiggers@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.