All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ranch <linux-hams@trinnet.net>
To: David Miller <davem@davemloft.net>, basil@pacabunga.com
Cc: jreuter@yaina.de, ralf@linux-mips.org,
	linux-hams@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: PATCH 1/1] AX.25: Close socket connection on session completion
Date: Mon, 4 Jul 2016 15:48:40 -0700	[thread overview]
Message-ID: <577AE7C8.3040806@trinnet.net> (raw)
In-Reply-To: <20160618.205545.1211200211643065140.davem@davemloft.net>


Hello David,

Unless I'm doing something wrong, it seems this patch has only been 
applied to the newest
kernel:

    Git/linux-stable$ git tag -l --contains 
4a7d99ea1b27734558feb6833f180cd38a159940
    v4.7-rc6

How can we get this critical fix applied to the other stable kernel 
versions?  I would really hate
to depend on all the various Distro packagers to miss on picking this up 
as this is a critical
toxicity fix.


Reference: http://www.spinics.net/lists/linux-hams/msg03628.html

--David




On 06/18/2016 08:55 PM, David Miller wrote:
> From: Basil Gunn <basil@pacabunga.com>
> Date: Thu, 16 Jun 2016 09:42:30 -0700
>
>> A socket connection made in ax.25 is not closed when session is
>> completed.  The heartbeat timer is stopped prematurely and this is
>> where the socket gets closed. Allow heatbeat timer to run to close
>> socket. Symptom occurs in kernels >= 4.2.0
>>
>> Originally sent 6/15/2016. Resend with distribution list matching
>> scripts/maintainer.pl output.
>>
>> Signed-off-by: Basil Gunn <basil@pacabunga.com>
> Applied.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2016-07-04 22:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-16 16:42 PATCH 1/1] AX.25: Close socket connection on session completion Basil Gunn
2016-06-17 18:33 ` David Miller
2016-06-19  0:44   ` David Ranch
2016-06-19  7:46   ` Thomas Osterried
2016-06-19  3:55 ` David Miller
2016-07-04 22:48   ` David Ranch [this message]
2016-07-04 23:31     ` David Miller

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=577AE7C8.3040806@trinnet.net \
    --to=linux-hams@trinnet.net \
    --cc=basil@pacabunga.com \
    --cc=davem@davemloft.net \
    --cc=jreuter@yaina.de \
    --cc=linux-hams@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=ralf@linux-mips.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.