[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170306121840.aaa0525d3dbdeb82aad3c284@linux-foundation.org>
Date: Mon, 6 Mar 2017 12:18:40 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Jens Axboe <axboe@...com>
Cc: Johannes Thumshirn <jthumshirn@...e.de>,
Minchan Kim <minchan@...nel.org>,
Nitin Gupta <ngupta@...are.org>,
Christoph Hellwig <hch@....de>,
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
Hannes Reinecke <hare@...e.de>, <yizhan@...hat.com>,
Linux Block Layer Mailinglist <linux-block@...r.kernel.org>,
Linux Kernel Mailinglist <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] zram: set physical queue limits to avoid array out of
bounds accesses
On Mon, 6 Mar 2017 08:21:11 -0700 Jens Axboe <axboe@...com> 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?
Powered by blists - more mailing lists