From: xinhui <xinhui@linux.vnet.ibm.com>
To: xinhui <xinhui.pan@linux.vnet.ibm.com>, linux-kernel@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
dvyukov@google.com, yanmin_zhang@linux.intel.com
Subject: Re: [PATCH] tty/n_gsm.c: fix false positive WARN_ON and do some codes improvement
Date: Wed, 25 Nov 2015 19:27:15 +0800 [thread overview]
Message-ID: <56559B13.40800@linux.vnet.ibm.com> (raw)
In-Reply-To: <5655990D.7090300@linux.vnet.ibm.com>
Hi, Jiri
I made this patch based on your idea. Any modification is welcome. :)
PS. "xinhui" or "xinhui.pan"@linux.vnet.ibm.com are same mail account, both of them are alias.
thanks
xinhui
On 2015/11/25 19:18, xinhui wrote:
> From: xinhui <xinhui@linux.vnet.ibm.com>
>
> If gsm driver fails to activate one mux, and this mux is not stored in
> gsm_mux[], there would be a warning in gsm_cleanup_mux(). Actually this
> is a legal case. So just do a simple check instead of WARN_ON.
>
> There is one filed gsm->num to store its index of gsm_mux[]. So use
> gsm->num to remove itself from gsm_mux[] instead of the for-loop
> traverse.
>
> Reported-by: Dmitry Vyukov <dvyukov@google.com>
> Fixes: 5a64096700dc ("tty/n_gsm.c: fix a memory leak in gsmld_open")
> Signed-off-by: Pan Xinhui <xinhui.pan@linux.vnet.ibm.com>
> ---
> drivers/tty/n_gsm.c | 12 +++++-------
> 1 files changed, 5 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/tty/n_gsm.c b/drivers/tty/n_gsm.c
> index c3fe026..56377e1 100644
> --- a/drivers/tty/n_gsm.c
> +++ b/drivers/tty/n_gsm.c
> @@ -2037,15 +2037,13 @@ static void gsm_cleanup_mux(struct gsm_mux *gsm)
>
> gsm->dead = 1;
>
> + /* open failed before registering => nothing to do*/
> + if (gsm_mux[gsm->num] != gsm)
> + return;
> +
> spin_lock(&gsm_mux_lock);
> - for (i = 0; i < MAX_MUX; i++) {
> - if (gsm_mux[i] == gsm) {
> - gsm_mux[i] = NULL;
> - break;
> - }
> - }
> + gsm_mux[gsm->num] = NULL;
> spin_unlock(&gsm_mux_lock);
> - WARN_ON(i == MAX_MUX);
>
> /* In theory disconnecting DLCI 0 is sufficient but for some
> modems this is apparently not the case. */
>
next prev parent reply other threads:[~2015-11-25 11:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 11:18 [PATCH] tty/n_gsm.c: fix false positive WARN_ON and do some codes improvement xinhui
2015-11-25 11:27 ` xinhui [this message]
2015-12-14 18:55 ` Greg Kroah-Hartman
2015-12-15 5:43 ` Pan Xinhui
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=56559B13.40800@linux.vnet.ibm.com \
--to=xinhui@linux.vnet.ibm.com \
--cc=dvyukov@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xinhui.pan@linux.vnet.ibm.com \
--cc=yanmin_zhang@linux.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