mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@kernel.org>
To: Wang Weiyang <wangweiyang2@huawei.com>,
	gregkh@linuxfoundation.org, sheng@linux.intel.com,
	bruce.j.beare@intel.com, xiaohui.xin@intel.com,
	yunhong.jiang@intel.com, arve@google.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tty: goldfish: Use tty_port_destroy() to destroy port
Date: Tue, 29 Mar 2022 08:13:50 +0200	[thread overview]
Message-ID: <b882ffc5-97df-7b26-4506-30ab7933d960@kernel.org> (raw)
In-Reply-To: <20220328115844.86032-1-wangweiyang2@huawei.com>

On 28. 03. 22, 13:58, Wang Weiyang wrote:
> In goldfish_tty_probe(), the port initialized through tty_port_init()
> should be destroyed in error paths.In goldfish_tty_remove(), qtty->port
> also should be destroyed or else might leak resources.
> 
> Fix the above by calling tty_port_destroy().

Reviewed-by: Jiri Slaby <jirislaby@kernel.org>

> Fixes: 666b7793d4bf ("goldfish: tty driver")
> Signed-off-by: Wang Weiyang <wangweiyang2@huawei.com>
> ---
>   drivers/tty/goldfish.c | 2 ++
>   1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/tty/goldfish.c b/drivers/tty/goldfish.c
> index ad13532e92fe..9e1168c39e77 100644
> --- a/drivers/tty/goldfish.c
> +++ b/drivers/tty/goldfish.c
> @@ -405,6 +405,7 @@ static int goldfish_tty_probe(struct platform_device *pdev)
>   err_tty_register_device_failed:
>   	free_irq(irq, qtty);
>   err_dec_line_count:
> +	tty_port_destroy(&qtty->port);
>   	goldfish_tty_current_line_count--;
>   	if (goldfish_tty_current_line_count == 0)
>   		goldfish_tty_delete_driver();
> @@ -426,6 +427,7 @@ static int goldfish_tty_remove(struct platform_device *pdev)
>   	iounmap(qtty->base);
>   	qtty->base = NULL;
>   	free_irq(qtty->irq, pdev);
> +	tty_port_destroy(&qtty->port);
>   	goldfish_tty_current_line_count--;
>   	if (goldfish_tty_current_line_count == 0)
>   		goldfish_tty_delete_driver();

thanks,
-- 
js
suse labs

      reply	other threads:[~2022-03-29  6:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-28 11:58 Wang Weiyang
2022-03-29  6:13 ` Jiri Slaby [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=b882ffc5-97df-7b26-4506-30ab7933d960@kernel.org \
    --to=jirislaby@kernel.org \
    --cc=arve@google.com \
    --cc=bruce.j.beare@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sheng@linux.intel.com \
    --cc=wangweiyang2@huawei.com \
    --cc=xiaohui.xin@intel.com \
    --cc=yunhong.jiang@intel.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

all inboxes | Powered by JetHome®