netdev - Re: missing in stable 4.1.1 - was Re: pull-request: can 2015-06-21

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 30 Jun 2015 14:20:55 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	socketcan@...tkopp.net
Cc:	stable@...r.kernel.org, gregkh@...uxfoundation.org,
	mkl@...gutronix.de, netdev@...r.kernel.org,
	linux-can@...r.kernel.org, kernel@...gutronix.de
Subject: Re: missing in stable 4.1.1 - was Re: pull-request: can 2015-06-21

From: Oliver Hartkopp <socketcan@...tkopp.net>
Date: Tue, 30 Jun 2015 21:31:36 +0200

> Hello Greg,
> 
> On 23.06.2015 15:43, David Miller wrote:
>> From: Marc Kleine-Budde <mkl@...gutronix.de>
>> Date: Sun, 21 Jun 2015 19:04:58 +0200
>>
>>> this is a, probably too late, pull request for v4.1.
>>>
>>> Oliver Hartkopp fixed a bug in the generic CAN frame handling code,
>>> which may
>>> lead to loss of CAN frames. It was introduced during v4.1 development.
>>>
>>> Please queue via net/master if possible, net-next/master
>>> otherwise. I've added
>>> stable on Cc, just in case.
>>
>> Pulled, thanks.
> 
> the patch "can: fix loss of CAN frames in raw_rcv" was sent to stable
> on 2015-06-21 but unfortunately did not find its way into 4.1.1 :-(
> 
> The upstream commit is:
> 
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=36c01245eb8046c16eee6431e7dbfbb302635fa8
> 
> which slipped into 4.2 at merge window opening time.
> 
> So it just got lost in the stable queue somehow.

Please take care of CAN -stable submissions yourself, thanks.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html