From: Hans de Goede <hdegoede@redhat.com>
To: Bo Liu <liubo03@inspur.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vboxsf: Directly use ida_alloc()/free()
Date: Wed, 15 Jun 2022 21:34:44 +0200 [thread overview]
Message-ID: <982a47a2-8340-a9e6-0a44-b132b94e0b52@redhat.com> (raw)
In-Reply-To: <20220615062930.2893-1-liubo03@inspur.com>
Hi,
On 6/15/22 08:29, Bo Liu wrote:
> Use ida_alloc()/ida_free() instead of
> ida_simple_get()/ida_simple_remove().
> The latter is deprecated and more verbose.
>
> Signed-off-by: Bo Liu <liubo03@inspur.com>
Thanks, patch looks good to me:
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
Regards,
Hans
> ---
> fs/vboxsf/super.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/fs/vboxsf/super.c b/fs/vboxsf/super.c
> index d2f6df69f611..24ef7ddecf89 100644
> --- a/fs/vboxsf/super.c
> +++ b/fs/vboxsf/super.c
> @@ -155,7 +155,7 @@ static int vboxsf_fill_super(struct super_block *sb, struct fs_context *fc)
> }
> }
>
> - sbi->bdi_id = ida_simple_get(&vboxsf_bdi_ida, 0, 0, GFP_KERNEL);
> + sbi->bdi_id = ida_alloc(&vboxsf_bdi_ida, GFP_KERNEL);
> if (sbi->bdi_id < 0) {
> err = sbi->bdi_id;
> goto fail_free;
> @@ -221,7 +221,7 @@ static int vboxsf_fill_super(struct super_block *sb, struct fs_context *fc)
> vboxsf_unmap_folder(sbi->root);
> fail_free:
> if (sbi->bdi_id >= 0)
> - ida_simple_remove(&vboxsf_bdi_ida, sbi->bdi_id);
> + ida_free(&vboxsf_bdi_ida, sbi->bdi_id);
> if (sbi->nls)
> unload_nls(sbi->nls);
> idr_destroy(&sbi->ino_idr);
> @@ -268,7 +268,7 @@ static void vboxsf_put_super(struct super_block *sb)
>
> vboxsf_unmap_folder(sbi->root);
> if (sbi->bdi_id >= 0)
> - ida_simple_remove(&vboxsf_bdi_ida, sbi->bdi_id);
> + ida_free(&vboxsf_bdi_ida, sbi->bdi_id);
> if (sbi->nls)
> unload_nls(sbi->nls);
>
prev parent reply other threads:[~2022-06-15 19:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 6:29 [PATCH] vboxsf: Directly use ida_alloc()/free() Bo Liu
2022-06-15 19:20 ` Christophe JAILLET
2022-06-15 19:34 ` Hans de Goede [this message]
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=982a47a2-8340-a9e6-0a44-b132b94e0b52@redhat.com \
--to=hdegoede@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liubo03@inspur.com \
/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;
as well as URLs for NNTP newsgroup(s).