[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160915221229.e25o5xw7bhbeixbe@thunk.org>
Date: Thu, 15 Sep 2016 18:12:29 -0400
From: Theodore Ts'o <tytso@....edu>
To: Jaegeuk Kim <jaegeuk@...nel.org>
Cc: Eric Biggers <ebiggers@...gle.com>, linux-fsdevel@...r.kernel.org,
linux-ext4@...r.kernel.org, linux-f2fs-devel@...ts.sourceforge.net
Subject: Re: [PATCH v2] fscrypto: make filename crypto functions return 0 on
success
On Thu, Sep 15, 2016 at 01:24:01PM -0700, Jaegeuk Kim wrote:
> On Thu, Sep 15, 2016 at 10:28:49AM -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'.
> >
> > Therefore, make these functions return 0 instead of a length, and make
> > the callers who cared about the return value being a length use
> > 'oname->len' instead. For consistency also make other callers check for
> > a nonzero result rather than a negative result.
> >
> > This change also fixes the inconsistency of fname_encrypt() actually
> > already returning 0 on success, not a length like the other filename
> > crypto functions and as documented in its function comment.
> >
> > Signed-off-by: Eric Biggers <ebiggers@...gle.com>
>
> Acked-by: Jaegeuk Kim <jaegeuk@...nel.org>
Thanks, applied.
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists