From: Thomas Osterried <thomas@osterried.de>
To: Roland Schwarz <roland.schwarz@blackspace.at>
Cc: duoming@zju.edu.cn, Thomas Osterried <thomas@osterried.de>,
linux-hams@vger.kernel.org
Subject: Re: Regression in "ax25: Fix UAF bugs in ax25 timers", patch 82e31755e55fbcea6a9dfaae5fe4860ade17cbc0
Date: Mon, 23 May 2022 20:53:33 +0200 [thread overview]
Message-ID: <YovYLRTLOJnVW4GP@x-berg.in-berlin.de> (raw)
In-Reply-To: <4e38f3dc-88f5-1df9-bdd4-f1d169d67439@blackspace.at>
On Mon, May 23, 2022 at 06:05:47PM +0200, Roland Schwarz wrote:
>
>
> On 23.05.22 at 16:07 wrote duoming@zju.edu.cn:
> ...>
> > Is there any ways to reproduce this problem?
> >
>
> As I understand it, the stuck LISTEN state is the
> infamous long-standing "stuck sockets" bug which
> Dave was pointing at in his mail "Status of the
> stuck sockets bugs" from 2021-06-29.
No, this is a new cause, resulting to the same
symtom (listening state ex-connected sessions).
As said, of you stop timers in cases you don't need
to, nothing tidies up (and nothing honors
the ax25 state machine).
There had been cases observed (since a few years).
I've seen such a case and have a fix I'll present
later. But let's resolve one after another,
not in parallel.
vy 73,
- Thomas dl9sau
next prev parent reply other threads:[~2022-05-23 18:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 5:46 Regression in "ax25: Fix UAF bugs in ax25 timers", patch 82e31755e55fbcea6a9dfaae5fe4860ade17cbc0 Thomas Osterried
2022-05-23 13:52 ` Dan Carpenter
2022-05-24 9:25 ` Thomas Osterried
2022-05-24 10:47 ` duoming
2022-05-24 21:52 ` Thomas Osterried
2022-05-25 2:34 ` duoming
2022-05-26 22:56 ` Thomas Osterried
2022-05-27 4:48 ` duoming
2022-05-23 14:07 ` duoming
2022-05-23 16:05 ` Roland Schwarz
2022-05-23 18:53 ` Thomas Osterried [this message]
2022-05-23 19:14 ` Thomas Osterried
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=YovYLRTLOJnVW4GP@x-berg.in-berlin.de \
--to=thomas@osterried.de \
--cc=duoming@zju.edu.cn \
--cc=linux-hams@vger.kernel.org \
--cc=roland.schwarz@blackspace.at \
/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.