From: Greg KH <gregkh@linuxfoundation.org>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Denis Grigorev <d.grigorev@omprussia.ru>, stable@vger.kernel.org
Subject: Re: 3.16 EOL
Date: Thu, 2 Jul 2020 18:49:31 +0200 [thread overview]
Message-ID: <20200702164931.GA2147773@kroah.com> (raw)
In-Reply-To: <514c425e2b4dca71a11b0c669746d3122f7039a5.camel@decadent.org.uk>
On Thu, Jul 02, 2020 at 03:55:04PM +0100, Ben Hutchings wrote:
> On Thu, 2020-07-02 at 09:39 +0200, Greg KH wrote:
> > On Thu, Jul 02, 2020 at 12:31:01AM +0100, Ben Hutchings wrote:
> > > On Tue, 2020-06-30 at 18:36 +0300, Denis Grigorev wrote:
> > > > This series of commits fixes a problem with closing l2cap connection
> > > > if socket has unACKed frames. Due an to an infinite loop in l2cap_wait_ack
> > > > the userspace process gets stuck in close() and then the kernel crashes
> > > > with the following report:
> > > >
> > > > Call trace:
> > > > [<ffffffc000ace0b4>] l2cap_do_send+0x2c/0xec
> > > > [<ffffffc000acf5f8>] l2cap_send_sframe+0x178/0x260
> > > > [<ffffffc000acf740>] l2cap_send_rr_or_rnr+0x60/0x84
> > > > [<ffffffc000acf980>] l2cap_ack_timeout+0x60/0xac
> > > > [<ffffffc0000b35b8>] process_one_work+0x140/0x384
> > > > [<ffffffc0000b393c>] worker_thread+0x140/0x4e4
> > > > [<ffffffc0000b8c48>] kthread+0xdc/0xf0
> > > >
> > > > All kernels below v4.3 are affected.
> > > [...]
> > >
> > > Thanks for your work, but I'm afraid the 3.16-stable branch is no
> > > longer being maintained (as of today).
> >
> > Want me to mark it EOL and remove it from the release table on
> > kernel.org now?
>
> I was about to send that patch myself, but you're welcome to do so.
Now done.
> Thanks again for all your assistance with releasing updates for 3.2 and
> 3.16 over the past 8 years.
Hey, thanks for doing all the real work there, that was a lot!
greg k-h
prev parent reply other threads:[~2020-07-02 16:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 15:36 [PATCH 3.16 00/10] Fix possible crash on L2CAP socket shutdown Denis Grigorev
2020-06-30 15:36 ` [PATCH 3.16 01/10] Bluetooth: Stop sabotaging list poisoning Denis Grigorev
2020-06-30 15:36 ` [PATCH 3.16 02/10] Bluetooth: Reinitialize the list after deletion for session user list Denis Grigorev
2020-06-30 15:36 ` [PATCH 3.16 03/10] Bluetooth: L2CAP ERTM shutdown protect sk and chan Denis Grigorev
2020-06-30 15:36 ` [PATCH 3.16 04/10] Bluetooth: Make __l2cap_wait_ack more efficient Denis Grigorev
2020-06-30 15:36 ` [PATCH 3.16 05/10] Bluetooth: Add BT_DBG to l2cap_sock_shutdown() Denis Grigorev
2020-06-30 15:36 ` [PATCH 3.16 06/10] Bluetooth: __l2cap_wait_ack() use msecs_to_jiffies() Denis Grigorev
2020-06-30 15:36 ` [PATCH 3.16 07/10] Bluetooth: __l2cap_wait_ack() add defensive timeout Denis Grigorev
2020-06-30 15:36 ` [PATCH 3.16 08/10] Bluetooth: Unwind l2cap_sock_shutdown() Denis Grigorev
2020-06-30 15:36 ` [PATCH 3.16 09/10] Bluetooth: Reorganize mutex lock in l2cap_sock_shutdown() Denis Grigorev
2020-06-30 15:36 ` [PATCH 3.16 10/10] Bluetooth: l2cap_disconnection_req priority over shutdown Denis Grigorev
2020-07-01 23:31 ` [PATCH 3.16 00/10] Fix possible crash on L2CAP socket shutdown Ben Hutchings
2020-07-02 7:39 ` Greg KH
2020-07-02 14:55 ` 3.16 EOL Ben Hutchings
2020-07-02 16:49 ` Greg KH [this message]
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=20200702164931.GA2147773@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ben@decadent.org.uk \
--cc=d.grigorev@omprussia.ru \
--cc=stable@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 NNTP newsgroup(s).