All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wang Weiyang <wangweiyang2@huawei.com>
To: <gregkh@linuxfoundation.org>, <jirislaby@kernel.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>, <wangweiyang2@huawei.com>
Subject: [PATCH] tty: goldfish: Use tty_port_destroy() to destroy port
Date: Mon, 28 Mar 2022 19:58:44 +0800	[thread overview]
Message-ID: <20220328115844.86032-1-wangweiyang2@huawei.com> (raw)

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().

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();
-- 
2.17.1


             reply	other threads:[~2022-03-28 11:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-28 11:58 Wang Weiyang [this message]
2022-03-29  6:13 ` [PATCH] tty: goldfish: Use tty_port_destroy() to destroy port Jiri Slaby

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=20220328115844.86032-1-wangweiyang2@huawei.com \
    --to=wangweiyang2@huawei.com \
    --cc=arve@google.com \
    --cc=bruce.j.beare@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sheng@linux.intel.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 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.