Re: [PATCH 3.16 00/10] Fix possible crash on L2CAP socket shutdown

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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?

thanks,

greg k-h



[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux