From: Chris Maness <christopher.maness@gmail.com>
To: "linux-hams@vger.kernel.org" <linux-hams@vger.kernel.org>
Subject: Backport to LTR?
Date: Sat, 11 Mar 2023 12:48:54 -0800 [thread overview]
Message-ID: <CANnsUMExojiA6ZNyH=_zjO44N4hR0ytqj-BWrRjO0L6Ox=MjsA@mail.gmail.com> (raw)
I am wondering what the process is to get maintainers to backport
AX.25 fixes to LTS kernels. Any suggestions? This is a diff I pulled
off the latest LTS kernel, so unfortunately it still has not been
committed.
diff linux-5.15.100/net/ax25/af_ax25.c linux-5.15.89/net/ax25/af_ax25.c
(I patched 5.15.89 by hand, and it has been working solid on both
x86_64 and also 64 bit Pi.
I am going to the latest release branch and see if runs my
Slackware-15 ok. I will keep my stuff as a fallback.
64a65
> spin_lock_bh(&ax25_list_lock);
66d66
< spin_lock_bh(&ax25_list_lock);
68d67
< spin_unlock_bh(&ax25_list_lock);
70a70
> spin_unlock_bh(&ax25_list_lock);
83a84
> ax25_dev->device_up = false;
93a95
> ax25_cb_del(s);
105a108
> ax25_cb_del(s);
998,1000c1001,1005
< release_sock(sk);
< ax25_disconnect(ax25, 0);
< lock_sock(sk);
---
> if (!sock_flag(ax25->sk, SOCK_DEAD)) {
> release_sock(sk);
> ax25_disconnect(ax25, 0);
> lock_sock(sk);
> }
1056,1060c1061,1067
< del_timer_sync(&ax25->timer);
< del_timer_sync(&ax25->t1timer);
< del_timer_sync(&ax25->t2timer);
< del_timer_sync(&ax25->t3timer);
< del_timer_sync(&ax25->idletimer);
---
> if (!ax25_dev->device_up) {
> del_timer_sync(&ax25->timer);
> del_timer_sync(&ax25->t1timer);
> del_timer_sync(&ax25->t2timer);
> del_timer_sync(&ax25->t3timer);
> del_timer_sync(&ax25->idletimer);
> }
--
Thanks,
Chris Maness
next reply other threads:[~2023-03-11 20:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 20:48 Chris Maness [this message]
2023-03-12 18:05 ` Backport to LTR? David Ranch
2023-03-13 4:23 ` Dan Carpenter
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='CANnsUMExojiA6ZNyH=_zjO44N4hR0ytqj-BWrRjO0L6Ox=MjsA@mail.gmail.com' \
--to=christopher.maness@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 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).