From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH] gatmux: fix channel remove on error.
Date: Tue, 04 Oct 2016 22:16:17 -0500 [thread overview]
Message-ID: <57F47081.9010406@gmail.com> (raw)
In-Reply-To: <413c78b0-58b5-42cc-0d2f-ec0615a83688@overkiz.com>
[-- Attachment #1: Type: text/plain, Size: 2109 bytes --]
Hi Antoine,
On 10/04/2016 02:42 AM, Antoine Aubert wrote:
> In case of invalid IO, read_watch is not reset. Fix crash on destroy
> gatmux.
>
> Signed-off-by: Antoine Aubert<a.aubert@overkiz.com>
We don't use Signed-off-by here. See HACKING, Submitting Patches section.
> ---
> gatchat/gatmux.c | 16 ++++++++++++----
> 1 file changed, 12 insertions(+), 4 deletions(-)
>
> diff --git a/gatchat/gatmux.c b/gatchat/gatmux.c
> index 9beeece..896ddff 100644
> --- a/gatchat/gatmux.c
> +++ b/gatchat/gatmux.c
> @@ -186,8 +186,10 @@ static gboolean received_data(GIOChannel *channel, GIOCondition cond,
> GIOStatus status;
> gsize bytes_read;
>
> - if (cond & G_IO_NVAL)
> + if (cond & G_IO_NVAL) {
> + mux->read_watch = 0;
> return FALSE;
> + }
Good catch on this one. However it might be easier solved by using a
watch destroy notify function. E.g. in g_at_mux_start():
mux->read_watch = g_io_add_watch_full(mux->channel,
G_PRIORITY_DEFAULT,
G_IO_IN | G_IO_HUP | G_IO_ERR | G_IO_NVAL,
received_data, mux, NULL);
The last NULL parameter should be set to a new function that resets the
mux->read_watch to 0. Similar to write_watcher_destroy_notify.
>
> debug(mux, "received data");
>
> @@ -223,14 +225,20 @@ static gboolean received_data(GIOChannel *channel, GIOCondition cond,
> }
> }
>
> - if (cond & (G_IO_HUP | G_IO_ERR))
> + if (cond & (G_IO_HUP | G_IO_ERR)) {
> + mux->read_watch = 0;
> return FALSE;
> + }
>
> - if (status != G_IO_STATUS_NORMAL && status != G_IO_STATUS_AGAIN)
> + if (status != G_IO_STATUS_NORMAL && status != G_IO_STATUS_AGAIN) {
> + mux->read_watch = 0;
> return FALSE;
> + }
>
> - if (mux->buf_used == sizeof(mux->buf))
> + if (mux->buf_used == sizeof(mux->buf)) {
> + mux->read_watch = 0;
> return FALSE;
> + }
That way all these redundant statements are handled by the destroy notify.
>
> return TRUE;
> }
> --
> 2.7.4
>
Care to resubmit?
Regards,
-Denis
next prev parent reply other threads:[~2016-10-05 3:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 7:42 [PATCH] gatmux: fix channel remove on error Antoine Aubert
2016-10-05 3:16 ` Denis Kenzior [this message]
2016-10-05 6:42 ` [PATCH] gatmux: fix read " Antoine Aubert
2016-10-05 18:04 ` Denis Kenzior
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=57F47081.9010406@gmail.com \
--to=denkenz@gmail.com \
--cc=ofono@ofono.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox