linux-kernel - Re: Support for TI FlashMedia (pci id 104c:8033, 104c:803b) flash card readers

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]

Message-ID: <44FC3B2E.106@drzeus.cx>
Date:	Mon, 04 Sep 2006 16:41:50 +0200
From:	Pierre Ossman <drzeus-list@...eus.cx>
To:	Alex Dubov <oakad@...oo.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: Support for TI FlashMedia (pci id 104c:8033, 104c:803b) flash
 card readers

Alex Dubov wrote:
>
> If I understand correctly, there should be two different ways to report bytes_xfered:
> 1. for read operations, the current block/byte counter reporting is sufficient
>   

It should be the number of successfully received bytes all the way to
the kernel. But this is difficult to get wrong. ;)

> 2. for write operation, error-less BUSY assert/de-assert pairs shall be counted instead
> Currently I only look at the last BUSY de-assert to verify that command is completed successfully.
> As mmc_block always issues single block writes it is sufficient. If this will ever change, more
> sophisticated scheme can be devised.
>
>   

This is about to change. Hence the need to check that all drivers are
reporting what they're supposed to.

Rgds
Pierre

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/