From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linuxfoundation.org ([140.211.169.12]:45594 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932350AbdCFVfy (ORCPT ); Mon, 6 Mar 2017 16:35:54 -0500 Date: Mon, 6 Mar 2017 12:18:40 -0800 From: Andrew Morton To: Jens Axboe Cc: Johannes Thumshirn , Minchan Kim , Nitin Gupta , Christoph Hellwig , Sergey Senozhatsky , Hannes Reinecke , , Linux Block Layer Mailinglist , Linux Kernel Mailinglist Subject: Re: [PATCH] zram: set physical queue limits to avoid array out of bounds accesses Message-Id: <20170306121840.aaa0525d3dbdeb82aad3c284@linux-foundation.org> In-Reply-To: <96ed9003-6299-b303-a901-d040a8cfe03f@fb.com> References: <20170306102335.9180-1-jthumshirn@suse.de> <96ed9003-6299-b303-a901-d040a8cfe03f@fb.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-block-owner@vger.kernel.org List-Id: linux-block@vger.kernel.org On Mon, 6 Mar 2017 08:21:11 -0700 Jens Axboe wrote: > On 03/06/2017 03:23 AM, Johannes Thumshirn wrote: > > zram can handle at most SECTORS_PER_PAGE sectors in a bio's bvec. When using > > the NVMe over Fabrics loopback target which potentially sends a huge bulk of > > pages attached to the bio's bvec this results in a kernel panic because of > > array out of bounds accesses in zram_decompress_page(). > > Applied, thanks. With an added cc:stable, hopefully?