linux-kernel - Re: [00/40] 3.0.17-stable review

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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 11 Jan 2012 17:21:58 -0500
From:	Nick Bowler <nbowler@...iptictech.com>
To:	Greg KH <gregkh@...e.de>
Cc:	linux-kernel@...r.kernel.org, stable@...r.kernel.org,
	torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
	alan@...rguk.ukuu.org.uk, "David S. Miller" <davem@...emloft.net>
Subject: Re: [00/40] 3.0.17-stable review

Hi Greg,

On 2012-01-10 13:46 -0800, Greg KH wrote:
> This is the start of the stable review cycle for the 3.0.17 release.
> There are 40 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied, please
> let us know.  If anyone is a maintainer of the proper subsystem, and
> wants to add a Signed-off-by: line to the patch, please respond with it.

These upstream commits (in 3.2):

  b7ea81a58adc ("ah: Read nexthdr value before overwriting it in ahash input callback.")
  069294e813ed ("ah: Correctly pass error codes in ahash output callback.")

made it into the 3.1.y series but they appear to not have made it into
3.0.y, where they're also applicable.  Also, the following one fixes a
real bug so it may be 3.0.y material, although I'm not sure if any
in-tree drivers can trigger it (this one requires a real ahash driver
for real hardware to trigger; unlike the previous two, cryptd won't do):

  4b90a603a1b2 ("ah: Don't return NET_XMIT_DROP on input")

Cheers,
-- 
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/