From: patchwork-bot+ofono@kernel.org
To: Denis Kenzior <denkenz@gmail.com>
Cc: ofono@lists.linux.dev, m.lyubimov@aqsi.ru
Subject: Re: [PATCH v3] gatchat: fix g_at_chat_unref in notify handler
Date: Thu, 25 Jan 2024 22:40:28 +0000 [thread overview]
Message-ID: <170622242802.17249.915335241490090244.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240124164838.605025-1-denkenz@gmail.com>
Hello:
This patch was applied to ofono.git (master)
by Denis Kenzior <denkenz@gmail.com>:
On Wed, 24 Jan 2024 10:47:07 -0600 you wrote:
> From: Maxim Lyubimov <m.lyubimov@aqsi.ru>
>
> If the new_bytes handler processes a modem shutdown URC, it results in
> a call to the g_at_chat_unref function, which includes a call to the
> chat_cleanup function, which clears the list of URC handlers that
> continue to be traversed after the current handler has completed, and
> may lead to errors. To correct the situation, the chat_cleanup function
> is not called in the at_chat_unref function if the in_read_handler flag
> is set. In the new_bytes function, if the destroyed flag is set, the
> chat_cleanup function is called before calling g_free. Additional
> checks have been added to the chat_cleanup function.
>
> [...]
Here is the summary with links:
- [v3] gatchat: fix g_at_chat_unref in notify handler
https://git.kernel.org/pub/scm/network/ofono/ofono.git/?id=c994bc96d9c5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-01-25 22:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 15:00 [PATCH] gatchat: fix g_at_chat_unref in notify handler Maxim Lyubimov
2024-01-24 16:47 ` [PATCH v3] " Denis Kenzior
2024-01-25 22:40 ` patchwork-bot+ofono [this message]
2024-01-24 16:52 ` [PATCH] " 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=170622242802.17249.915335241490090244.git-patchwork-notify@kernel.org \
--to=patchwork-bot+ofono@kernel.org \
--cc=denkenz@gmail.com \
--cc=m.lyubimov@aqsi.ru \
--cc=ofono@lists.linux.dev \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).