From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: Joe Perches <joe@perches.com>, <ntfs3@lists.linux.dev>
Cc: <linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 1/3] fs/ntfs3: Refactoring of indx_find function
Date: Mon, 30 May 2022 20:11:24 +0300 [thread overview]
Message-ID: <075d601a-1d79-acbd-2d03-92a1a73cf9c7@paragon-software.com> (raw)
In-Reply-To: <94dd870e498e89e0998dee4dd0dbaaa4b4497929.camel@perches.com>
Hello.
Thanks for your input.
It's nice to have a clear typical return value, so I've updated patch.
On 5/27/22 19:07, Joe Perches wrote:
> On Fri, 2022-05-27 at 17:21 +0300, Almaz Alexandrovich wrote:
>> This commit makes function a bit more readable
>
> trivia:
>
>> diff --git a/fs/ntfs3/index.c b/fs/ntfs3/index.c
> []
>> @@ -1042,19 +1042,16 @@ int indx_find(struct ntfs_index *indx, struct ntfs_inode *ni,
>> {
>> int err;
>> struct NTFS_DE *e;
>> - const struct INDEX_HDR *hdr;
>> struct indx_node *node;
>>
>> if (!root)
>> root = indx_get_root(&ni->dir, ni, NULL, NULL);
>>
>> if (!root) {
>> - err = -EINVAL;
>> - goto out;
>> + /* Should not happed. */
>> + return -EINVAL;
>
> s/happed/happen/
>
>> for (;;) {
>> node = NULL;
>> if (*diff >= 0 || !de_has_vcn_ex(e)) {
>> *entry = e;
>> - goto out;
>> + return 0;
>> }
>
> might be nicer with a break; or a while like
>
> while (*diff < 0 && de_has_vcn_ex(e)) {
> node = NULL;
>
>
>> /* Read next level. */
>> err = indx_read(indx, ni, de_get_vbn(e), &node);
>> if (err)
>> - goto out;
>> + return err;
>>
>> /* Lookup entry that is <= to the search value. */
>> e = hdr_find_e(indx, &node->index->ihdr, key, key_len, ctx,
>> diff);
>> if (!e) {
>> - err = -EINVAL;
>> put_indx_node(node);
>> - goto out;
>> + return -EINVAL;
>> }
>>
>> fnd_push(fnd, node, e);
>> }
>> -
>> -out:
>> - return err;
>
> and a return 0;
>
> or
> *entry = e;
> return 0;
>
> so it appears that the function has a typical return value.
>
next prev parent reply other threads:[~2022-05-30 17:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 14:15 [PATCH 0/3] fs/ntfs3: Refactoring and bugfix Almaz Alexandrovich
2022-05-27 14:21 ` [PATCH 1/3] fs/ntfs3: Refactoring of indx_find function Almaz Alexandrovich
2022-05-27 16:07 ` Joe Perches
2022-05-30 17:11 ` Konstantin Komarov [this message]
2022-05-28 0:06 ` Dave Chinner
2022-05-30 16:15 ` Konstantin Komarov
2022-05-27 14:22 ` [PATCH 2/3] fs/ntfs3: Fix double free on remount Almaz Alexandrovich
2022-05-27 14:22 ` [PATCH 3/3] fs/ntfs3: Refactor ni_try_remove_attr_list function Almaz Alexandrovich
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=075d601a-1d79-acbd-2d03-92a1a73cf9c7@paragon-software.com \
--to=almaz.alexandrovich@paragon-software.com \
--cc=joe@perches.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
/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