[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bffdf6fc-becb-32c7-2669-fb18ebc3e172@fb.com>
Date: Mon, 6 Mar 2017 13:19:56 -0700
From: Jens Axboe <axboe@...com>
To: Andrew Morton <akpm@...ux-foundation.org>
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 03/06/2017 01:18 PM, Andrew Morton wrote:
> 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?
I didn't. But I can email it to stable@ when it lands in Linus's tree.
--
Jens Axboe
Powered by blists - more mailing lists