linux-kernel - Re: [PATCH] zram: fix data corruption issue

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:	Sat, 5 Feb 2011 21:11:11 -0800
From:	Greg KH <greg@...ah.com>
To:	Nitin Gupta <ngupta@...are.org>
Cc:	Pekka Enberg <penberg@...helsinki.fi>,
	Linux Driver Project <devel@...uxdriverproject.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] zram: fix data corruption issue

On Sun, Feb 06, 2011 at 12:03:12AM -0500, Nitin Gupta wrote:
> On 02/06/2011 12:00 AM, Greg KH wrote:
> >On Sat, Feb 05, 2011 at 08:34:20PM -0500, Nitin Gupta wrote:
> >>In zram_read() and zram_write() we were not incrementing the
> >>index number and thus were reading/writing values from/to
> >>incorrect sectors on zram disk, resulting in data corruption.
> >
> >Is this something that needs to go into .38 or can it wait until .39?
> >
> 
> 
> This really needs to get into .38 or users will see random data
> corruption on zram devices.

Ok, I'll queue it up for there.  What about .37 and/or .36?

thanks,

greg k-h
--
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/