From: Ralf Baechle <ralf@linux-mips.org>
To: Dave van der Locht <d.vanderlocht@gmail.com>
Cc: linux-hams@vger.kernel.org
Subject: Re: Status of the stuck sockets bugs.
Date: Fri, 23 Jul 2021 10:19:53 +0200 [thread overview]
Message-ID: <YPp7qeWGSW/s4TI6@linux-mips.org> (raw)
In-Reply-To: <CAH4uzPNOLbAvEW2XA=ReHn_ZnGM3rgRif9uTNxYB-eSpv9YD7A@mail.gmail.com>
On Thu, Jul 22, 2021 at 07:42:18PM +0200, Dave van der Locht wrote:
> Is anybody able to tell me more / give answers to questions about this issue?
>
> Kind regards,
> Dave van der Locht
>
> Op di 29 jun. 2021 om 19:32 schreef Dave van der Locht
> <d.vanderlocht@gmail.com>:
> >
> > Hello,
> >
> > Is there any news about the well known bug regarding sockets getting
> > stuck in LISTENING state?
> >
> > Some years ago (already) Marius Petrescu YO2LOJ wrote a patch for the
> > ax25_subr.c file which seems to work very well and solves the issue.
> > But it's really annoying having to patch the kernel with each update
> > again.
> >
> > What about that patch, I've heard it was rejected several times for
> > some reason? But can't find info regarding that.
> > What can be done - or who is able - to get rid of this bug and get it
> > fixed in the kernel?
I wasn't even aware of these patches and an internet search didn't turn
up anything. Fortunately it turned out I have friends who happen to
know Marius so who pointed me at his "patches" really quickly.
And they were not even patches but a broken out net/ax25 directory from
a Debian kernel with random changes. That said, while the way these
changes were hidden away and present leaves space for improvments,
technically they appear to have benefit, so I'm now working through
them.
Ralf
next prev parent reply other threads:[~2021-07-23 8:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 17:32 Status of the stuck sockets bugs Dave van der Locht
2021-07-22 17:42 ` Dave van der Locht
2021-07-22 23:22 ` David Ranch
2021-07-23 8:14 ` Ralf Baechle
2021-07-23 19:09 ` David Ranch
2021-07-24 6:44 ` Dave van der Locht
2021-07-23 8:19 ` Ralf Baechle [this message]
[not found] ` <CAH4uzPMp_4bwPf0+tjviM=5aDVGLRKfz+fC_gVybujwKriF48A@mail.gmail.com>
2021-07-23 8:49 ` Dave van der Locht
[not found] ` <CAH4uzPOuGD939KgYW5Rwn2or_xNtpo=TuAcCS6dbhrJ7GdZyQQ@mail.gmail.com>
2021-07-23 8:50 ` Dave van der Locht
2021-07-30 11:47 ` Roland Schwarz
2021-07-31 16:05 ` Roland Schwarz
2021-10-15 9:21 ` Dave van der Locht
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=YPp7qeWGSW/s4TI6@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=d.vanderlocht@gmail.com \
--cc=linux-hams@vger.kernel.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 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.