linux-kernel - Re: MMC layer regression with single-block controllers

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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 24 Mar 2009 21:01:38 +0100
From:	Pierre Ossman <drzeus@...eus.cx>
To:	Manuel Lauss <mano@...rinelk.homelinux.net>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: MMC layer regression with single-block controllers

On Mon, 23 Mar 2009 10:28:02 +0100
Manuel Lauss <mano@...rinelk.homelinux.net> wrote:

> Hello Pierre,
> 
> Since about 2.6.28-rc1, I hit the following BUG_ON() in mmc/core.c
> (line 155):
> 
>         if (mrq->data) {
>                 BUG_ON(mrq->data->blksz > host->max_blk_size);
> >>>>>>>>>       BUG_ON(mrq->data->blocks > host->max_blk_count);  <<<<<<
>                 BUG_ON(mrq->data->blocks * mrq->data->blksz >
>                         host->max_req_size);
> 
> It's easy to reproduce; just set your favorite host controllers'
> mmc->max_blk_cnt to 1 (or anything smaller than 4).  As far as I can
> tell it was introduced with some block layer changes before 2.6.28-rc1
> was released.
> 

Ouch. Have you determined that it is the block layer that isn't
respecting its settings? If so, the we probably need to notify Jens
Axboe.

Rgds
-- 
     -- Pierre Ossman

  WARNING: This correspondence is being monitored by the
  Swedish government. Make sure your server uses encryption
  for SMTP traffic and consider using PGP for end-to-end
  encryption.

Download attachment "signature.asc" of type "application/pgp-signature" (199 bytes)