On Mon, Jan 30, 2017 at 2:05 PM, Linus Walleij <[email protected]> wrote: > On Fri, Jan 27, 2017 at 8:58 AM, Ulf Hansson <[email protected]> wrote:
> And now it is crashing at mmc_blk_rw_rq_prep() + 0x20 so I suspect it is one > of > these: > > struct mmc_blk_request *brq = &mqrq->brq; > struct request *req = mqrq->req; > struct mmc_blk_data *md = mq->blkdata; > > I guess the first: mqrq is NULL. > > So I suspect the oneliner in commit 0ebd6e72b5ee2592625d5ae567a729345dfe07b6 > "mmc: block: do not assign mq_rq when aborting command" Bah looking closer at that it just doesn't make any logical sense at all. I now suspect the NULL check removed in mmc_blk_rw_start_new() to be behind this, so sent a patch to restore it. No idea how to test it or if it's the real problem. I had to rebase my further patches on top too, so if you merge this I need to resend the next series. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-block" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
