From: Jiri Slaby <jslaby@suse.cz>
To: Alexey Khoroshilov <khoroshilov@ispras.ru>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, ldv-project@linuxtesting.org
Subject: Re: [PATCH v2] tty: mxser: improve error handling in mxser_probe() and mxser_module_init()
Date: Thu, 28 Mar 2013 16:16:00 +0100 [thread overview]
Message-ID: <51545EB0.7020600@suse.cz> (raw)
In-Reply-To: <1361253463-30627-1-git-send-email-khoroshilov@ispras.ru>
Hi, back from Rome, I suppose ;).
On 02/19/2013 06:57 AM, Alexey Khoroshilov wrote:
> 1. Currently mxser_probe() and mxser_module_init() ignore errors
> that can happen in tty_port_register_device().
> 2. mxser_module_init() does not deallocate resources allocated in mxser_get_ISA_conf()
> if mxser_initbrd() failed.
>
> The patch adds proper error handling in all the cases.
> Also it moves free_irq() from mxser_release_ISA_res() to mxser_board_remove(),
> since it makes mxser_release_ISA_res() a counterpart for mxser_get_ISA_conf(),
> while free_irq() is relevant to both ISA and PCI boards.
>
> Found by Linux Driver Verification project (linuxtesting.org).
>
> Signed-off-by: Alexey Khoroshilov <khoroshilov@ispras.ru>
> ---
> drivers/tty/mxser.c | 42 +++++++++++++++++++++++++++++++++++-------
> 1 file changed, 35 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/tty/mxser.c b/drivers/tty/mxser.c
> index 4011386..deeb5ad 100644
> --- a/drivers/tty/mxser.c
> +++ b/drivers/tty/mxser.c
> @@ -2364,7 +2364,6 @@ static void mxser_release_vector(struct mxser_board *brd)
>
> static void mxser_release_ISA_res(struct mxser_board *brd)
> {
> - free_irq(brd->irq, brd);
> release_region(brd->ports[0].ioaddr, 8 * brd->info->nports);
> mxser_release_vector(brd);
> }
> @@ -2430,6 +2429,7 @@ static void mxser_board_remove(struct mxser_board *brd)
> tty_unregister_device(mxvar_sdriver, brd->idx + i);
> tty_port_destroy(&brd->ports[i].port);
> }
> + free_irq(brd->irq, brd);
> }
>
> static int __init mxser_get_ISA_conf(int cap, struct mxser_board *brd)
> @@ -2554,6 +2554,7 @@ static int mxser_probe(struct pci_dev *pdev,
> struct mxser_board *brd;
> unsigned int i, j;
> unsigned long ioaddress;
> + struct device *tty_dev;
> int retval = -EINVAL;
>
> for (i = 0; i < MXSER_BOARDS; i++)
> @@ -2637,13 +2638,25 @@ static int mxser_probe(struct pci_dev *pdev,
> if (retval)
> goto err_rel3;
>
> - for (i = 0; i < brd->info->nports; i++)
> - tty_port_register_device(&brd->ports[i].port, mxvar_sdriver,
> - brd->idx + i, &pdev->dev);
> + for (i = 0; i < brd->info->nports; i++) {
> + tty_dev = tty_port_register_device(&brd->ports[i].port,
> + mxvar_sdriver, brd->idx + i, &pdev->dev);
> + if (IS_ERR(tty_dev)) {
> + retval = PTR_ERR(tty_dev);
> + for (; i > 0; i--)
To me, it seems that v1 of the patch was merged. Could you fix this up?
[Coverity revealed this.]
thanks,
--
js
suse labs
next prev parent reply other threads:[~2013-03-28 15:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51228a02.BjrxclRZRRerxqem%fengguang.wu@intel.com>
2013-02-19 5:57 ` [PATCH v2] tty: mxser: improve error handling in mxser_probe() and mxser_module_init() Alexey Khoroshilov
2013-02-19 13:02 ` Jiri Slaby
2013-03-28 15:16 ` Jiri Slaby [this message]
2013-04-07 19:46 ` [PATCH] tty: mxser: fix cycle termination condition " Alexey Khoroshilov
2013-04-08 7:18 ` 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=51545EB0.7020600@suse.cz \
--to=jslaby@suse.cz \
--cc=gregkh@linuxfoundation.org \
--cc=khoroshilov@ispras.ru \
--cc=ldv-project@linuxtesting.org \
--cc=linux-kernel@vger.kernel.org \
/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.