stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nitin Gupta <ngupta@vflare.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Seth Jennings <sjenning@linux.vnet.ibm.com>,
	Jerome Marchand <jmarchan@redhat.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	stable@vger.kernel.org, Minchan Kim <minchan.kim@gmail.com>,
	Linux Driver Project <devel@linuxdriverproject.org>,
	Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: zram: fix invalid memory references during disk write
Date: Wed, 19 Dec 2012 07:53:36 -0800	[thread overview]
Message-ID: <50D1E300.4000006@vflare.org> (raw)
In-Reply-To: <20121219150826.GA23953@kroah.com>

On 12/19/2012 07:08 AM, Greg KH wrote:
> On Tue, Dec 18, 2012 at 11:21:28PM -0800, Nitin Gupta wrote:
>> On 12/18/2012 07:49 PM, Greg KH wrote:
>>> On Tue, Dec 18, 2012 at 01:12:05PM -0800, Nitin Gupta wrote:
>>>> On Tue, Dec 11, 2012 at 10:27 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
>>>>> On Thu, Nov 29, 2012 at 10:45:09PM -0800, Nitin Gupta wrote:
>>>>>> Fixes a bug introduced by commit c8f2f0db1 ("zram: Fix handling
>>>>>> of incompressible pages") which caused invalid memory references
>>>>>> during disk write. Invalid references could occur in two cases:
>>>>>>  - Incoming data expands on compression: In this case, reference was
>>>>>> made to kunmap()'ed bio page.
>>>>>>  - Partial (non PAGE_SIZE) write with incompressible data: In this
>>>>>> case, reference was made to a kfree()'ed buffer.
>>>>>>
>>>>>> Fixes bug 50081:
>>>>>> https://bugzilla.kernel.org/show_bug.cgi?id=50081
>>>>>>
>>>>>> Upstream commit ID: c8f2f0d: zram: Fix handling of incompressible pages
>>>>>> Apply to versions: 3.6.5, 3.6.6, 3.6.7, 3.6.8
>>>>>>
>>>>>> Cc: <stable@vger.kernel.org> # staging-next: 37b51fd: zram: factor-out
>>>>>>                               # zram_decompress_page() function
>>>>>> Signed-off-by: Nitin Gupta <ngupta@vflare.org>
>>>>>> Reported-by: Mihail Kasadjikov <hamer.mk@gmail.com>
>>>>>> Reported-by: Tomas M <tomas@slax.org>
>>>>>> Reviewed-by: Minchan Kim <minchan@kernel.org>
>>>>>> ---
>>>>>>  drivers/staging/zram/zram_drv.c |   39 ++++++++++++++++++++++++---------------
>>>>>>  1 file changed, 24 insertions(+), 15 deletions(-)
>>>>>
>>>>> This patch fails to apply to 3.6.10:
>>>>>
>>>>> patching file drivers/staging/zram/zram_drv.c
>>>>> Hunk #1 succeeded at 282 (offset 17 lines).
>>>>> Hunk #2 FAILED at 286.
>>>>> Hunk #3 succeeded at 319 (offset 17 lines).
>>>>> Hunk #4 succeeded at 340 (offset 17 lines).
>>>>> Hunk #5 succeeded at 353 (offset 17 lines).
>>>>> Hunk #6 succeeded at 368 (offset 17 lines).
>>>>> Hunk #7 succeeded at 385 (offset 17 lines).
>>>>> 1 out of 7 hunks FAILED -- saving rejects to file drivers/staging/zram/zram_drv.c.rej
>>>>>
>>>>> Please redo this patch and resend it if you wish for it to be applied to
>>>>> the 3.6-stable tree.
>>>>>
>>>>>
>>>>
>>>> Please apply this patch to stable tree asap.
>>>
>>> 3.6 is now end-of-life, there will not be any more releases for that
>>> kernel series anymore, sorry.
>>>
>>
>> Then please apply to 3.7.
> 
> That is impossible to do so, for the obvious reason.
> 

I meant to include it in whatever 3.7.x is released in future. Or put it
in staging, so it may eventually make it to mainline (by 3.8?).


Nitin


  reply	other threads:[~2012-12-19 15:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1354257909-2380-1-git-send-email-ngupta@vflare.org>
2012-11-30  6:58 ` zram: fix invalid memory references during disk write Nitin Gupta
2012-12-08  0:50 ` Nitin Gupta
2012-12-08 19:47   ` Greg KH
     [not found] ` <20121211182720.GC29421@kroah.com>
2012-12-18 21:12   ` Nitin Gupta
2012-12-19  3:49     ` Greg KH
2012-12-19  7:21       ` Nitin Gupta
2012-12-19 15:08         ` Greg KH
2012-12-19 15:53           ` Nitin Gupta [this message]
2012-12-19 16:17             ` Greg KH
2012-12-19 17:21               ` Nitin Gupta
2012-12-19 17:39                 ` Mitch Harder
2012-12-20 22:48                   ` Nitin Gupta
2013-01-14 19:19                   ` Greg KH
2013-01-15  0:48                     ` Nitin Gupta
2013-01-15 12:33                       ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50D1E300.4000006@vflare.org \
    --to=ngupta@vflare.org \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jmarchan@redhat.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minchan.kim@gmail.com \
    --cc=sjenning@linux.vnet.ibm.com \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).