linux-kernel - Re: [PATCH] ata: implement MODE SELECT command

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 for Android: free password hash cracker in your pocket

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

Message-ID: <4FF49AD7.20102@redhat.com>
Date:	Wed, 04 Jul 2012 21:34:47 +0200
From:	Paolo Bonzini <pbonzini@...hat.com>
To:	Sergei Shtylyov <sshtylyov@...sta.com>
CC:	linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org,
	Jeff Garzik <jgarzik@...ox.com>
Subject: Re: [PATCH] ata: implement MODE SELECT command

Il 04/07/2012 19:20, Sergei Shtylyov ha scritto:
>> > Perhaps for MODE SENSE, but not for MODE SELECT.  Otherwise, where do
>> > you get the mode data from?
>    They simply don't change?

The standard says "If the parameter list length results in the
truncation of any mode parameter header, mode parameter block
descriptor(s), or mode page, then the command shall be terminated with
CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and
the additional sense code set to PARAMETER LIST LENGTH ERROR".

Paolo
--
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/