linux-kernel - Re: WARNING: CPU: 0 PID: 1271 at drivers/mmc/core/core.c:991 mmc_release

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CALAqxLXmh0xEgAtQ5yiZqerOX_-uQVe8B4PvUN+ZgXDNA1JKGg@mail.gmail.com>
Date:	Fri, 12 Aug 2016 16:34:16 -0700
From:	John Stultz <john.stultz@...aro.org>
To:	Shawn Lin <shawn.lin@...k-chips.com>
Cc:	Jaehoon Chung <jh80.chung@...sung.com>,
	Ulf Hansson <ulf.hansson@...aro.org>,
	Guodong Xu <guodong.xu@...aro.org>,
	lkml <linux-kernel@...r.kernel.org>,
	Zhangfei Gao <zhangfei.gao@...aro.org>
Subject: Re: WARNING: CPU: 0 PID: 1271 at drivers/mmc/core/core.c:991 mmc_release_host+0xa0/0xa8

On Fri, Aug 12, 2016 at 1:30 AM, Shawn Lin <shawn.lin@...k-chips.com> wrote:
> If special req meets, mrq_pre and mrq_cur are both null after schedule
> queue. And for this special req, host->claimed is released. For the
> next req peeking from blk, we run into mmc_get_card again which means
> we should never meet this WARN when releasing host. So it's
> interesting to dig out actually what is happening there...
>
> But at least for dw_mmc-rockchip, we have been using this feature,
> ERASE/Trim/discard, for years. I didn't see it ever. Anyway from the
> code I was reading, I don't think it should be issue of this commit.
>
> Please look at this regression report I saw.
>
> https://lkml.org/lkml/2016/8/11/130

Hrm. Unfortunately I was still able to trigger the issue with the fix
from that mail.

thanks
-john