linux-kernel - Re: [PATCH][MMC] Fix wrong EXT_CSD

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: <9c9fda240712131801w5aec854eg71f3dc7ad49ddeb@mail.gmail.com>
Date:	Fri, 14 Dec 2007 11:01:03 +0900
From:	"Kyungmin Park" <kmpark@...radead.org>
To:	"Pierre Ossman" <drzeus-list@...eus.cx>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH][MMC] Fix wrong EXT_CSD_REV handling

On Dec 13, 2007 5:24 PM, Pierre Ossman <drzeus-list@...eus.cx> wrote:
> On Thu, 13 Dec 2007 17:08:16 +0900
> "Kyungmin Park" <kmpark@...radead.org> wrote:
>
> >
> > In my MMC Spec. (v4.2), there's no problem to read it even though it's
> > revision 1.1
> >
>
> Well, the spec says that those reserved fields "should be zero". Unfortunately, people seem to have read this in the IETF sense and not as "the fields MUST be zero". I.e. I've seen cards where reserved fields contain junk.
>

Yes, reserved word should or must be zero, then it should check "if
(ext_csd_struct <= 2)" instead of ">= 2".
In the Spec. 4.2, it can have three value 0, 1, or 2. There's no other
restriction.

Thank you,
Kyungmin Park.
--
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/