subject:"stable 3.0 and CVEs"

Re: stable 3.0 and CVEs

2013-03-19 Thread Jiri Slaby

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/18/2013 03:18 AM, Ben Hutchings wrote: > I reviewed your list against 3.2.y: > > On Fri, 2013-03-15 at 09:27 +0100, Jiri Slaby wrote: >> Hi, >> >> we have the following commits from usptream in a

Re: stable 3.0 and CVEs

2013-03-17 Thread Ben Hutchings

I reviewed your list against 3.2.y: On Fri, 2013-03-15 at 09:27 +0100, Jiri Slaby wrote: > Hi, > > we have the following commits from usptream in a SLE11sp2 kernel (3.0) > to fix various CVEs: > Git-commit: 3118a4f652c7b12c752f3222af0447008f9b2368 What's that then? > Git-commit: b0de59b5733d18b

Re: stable 3.0 and CVEs

2013-03-15 Thread Greg KH

On Fri, Mar 15, 2013 at 09:27:02AM +0100, Jiri Slaby wrote: > Hi, > > we have the following commits from usptream in a SLE11sp2 kernel (3.0) > to fix various CVEs: > Git-commit: 3118a4f652c7b12c752f3222af0447008f9b2368 > Git-commit: b0de59b5733d18b0d1974a060860a8b5c1b36a2e > Git-commit: b5a1eeef04

stable 3.0 and CVEs

2013-03-15 Thread Jiri Slaby

Hi, we have the following commits from usptream in a SLE11sp2 kernel (3.0) to fix various CVEs: Git-commit: 3118a4f652c7b12c752f3222af0447008f9b2368 Git-commit: b0de59b5733d18b0d1974a060860a8b5c1b36a2e Git-commit: b5a1eeef04cc7859f34dec9b72ea1b28e4aba07c Git-commit: c00b6856fc642b234895cfabd15b289