[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170907104749.p2bk6lejj7tvupor@macchiaveli>
Date: Thu, 7 Sep 2017 12:47:49 +0200
From: Seraphime Kirkovski <kirkseraph@...il.com>
To: Adrian Hunter <adrian.hunter@...el.com>
Cc: Ulf Hansson <ulf.hansson@...aro.org>,
Shawn Lin <shawn.lin@...k-chips.com>,
Pavel Machek <pavel@....cz>,
"linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
kernel list <linux-kernel@...r.kernel.org>,
Linus Walleij <linus.walleij@...aro.org>
Subject: 4.13 on thinkpad x220: oops when writing to SD card
> blk_init_allocated_queue() allocates 1 request for flush and
> 4 requests
> for a memory pool. The memory pool requests only get used under memory
> pressure. That is why the error doesn't come up straight away.
This seems correct, I can "trivially" trigger the bug with
a while-malloc loop + firefox.
> Reported-by: Seraphime Kirkovski <kirkseraph@...il.com>
> Fixes: 304419d8a7e92 ("mmc: core: Allocate per-request data using the block layer core")
> Signed-off-by: Adrian Hunter <adrian.hunter@...el.com>
As I said, this fixes it for me, you can add
Tested-By: Seraphime Kirkovski <kirkseraph@...il.com>
Although I'm not sure this covers the same bug Pavel encountered.
My kernel doesn't panic, it makes KASAN scream + #GP eventually followed
by a lockup.
Anyway, thanks for the fix,
Seraphime
Powered by blists - more mailing lists