From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Pan Xinhui <xinhui.pan@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
yanmin_zhang@linux.intel.com, mnipxh@163.com
Subject: Re: [PATCH resend ] tty/n_gsm.c: use gsm->num to remove mux itself from gsm_mux[]
Date: Mon, 14 Dec 2015 15:40:35 +0000 [thread overview]
Message-ID: <20151214154035.15ebb75a@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <566E6AD3.1060003@linux.vnet.ibm.com>
On Mon, 14 Dec 2015 15:08:03 +0800
Pan Xinhui <xinhui.pan@linux.vnet.ibm.com> wrote:
> From: Pan Xinhui <xinhui.pan@linux.vnet.ibm.com>
>
> There is one filed gsm->num to store mux's index of gsm_mux[]. So use
> gsm->num to remove itself from gsm_mux[] instead of the for-loop
> traverse in gsm_cleanup_mux().
>
> Signed-off-by: Pan Xinhui <xinhui.pan@linux.vnet.ibm.com>
> ---
> drivers/tty/n_gsm.c | 14 +++++---------
> 1 files changed, 5 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/tty/n_gsm.c b/drivers/tty/n_gsm.c
> index 9aff371..cf28054 100644
> --- a/drivers/tty/n_gsm.c
> +++ b/drivers/tty/n_gsm.c
> @@ -2037,18 +2037,14 @@ static void gsm_cleanup_mux(struct gsm_mux *gsm)
>
> gsm->dead = 1;
>
> - spin_lock(&gsm_mux_lock);
> - for (i = 0; i < MAX_MUX; i++) {
> - if (gsm_mux[i] == gsm) {
> - gsm_mux[i] = NULL;
> - break;
> - }
> - }
> - spin_unlock(&gsm_mux_lock);
> /* open failed before registering => nothing to do */
> - if (i == MAX_MUX)
> + if (gsm_mux[gsm->num] != gsm)
> return;
>
> + spin_lock(&gsm_mux_lock);
> + gsm_mux[gsm->num] = NULL;
> + spin_unlock(&gsm_mux_lock);
Its a highly theoretical and probably impossible corner case but I can't
help thinking the lock should be held for the if () as well as NULLing
this out.
Alan
next prev parent reply other threads:[~2015-12-14 15:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 7:08 Pan Xinhui
2015-12-14 15:40 ` One Thousand Gnomes [this message]
[not found] ` <398d6e8b.12b08.151b53d2775.Coremail.mnipxh@163.com>
2016-01-05 6:35 ` 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=20151214154035.15ebb75a@lxorguk.ukuu.org.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mnipxh@163.com \
--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
all inboxes | Powered by JetHome®