mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Hannes Reinecke <hare@suse.de>, Gleb Natapov <gleb@redhat.com>,
	"H. Peter Anvin" <hpa@linux.intel.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: [PATCH] EDD: Check for correct EDD 3.0 length
Date: Wed, 16 May 2012 08:51:36 +0200	[thread overview]
Message-ID: <1337151096-38511-1-git-send-email-hare@suse.de> (raw)

There are two competing EDD 3.0 specifications,
the original one from Phoenix
<http://mbldr.sourceforge.net/specsedd30.pdf>
and the T-13 approved one
<http://www.t13.org/documents/UploadedDocuments/docs2004/d1572r3-EDD3.pdf>

They differ in the length of the device_path field, which
is one quad word for the Phoenix spec and two quad words
for the T-13 spec. So we need to test for both lengths
and blank out the second quad word when a Phoenix
version is detected.

Signed-off-by: Hannes Reinecke <hare@suse.de>
Cc: Gleb Natapov <gleb@redhat.com>
Cc: H. Peter Anvin <hpa@linux.intel.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>

diff --git a/drivers/firmware/edd.c b/drivers/firmware/edd.c
index e229576..beedf4c 100644
--- a/drivers/firmware/edd.c
+++ b/drivers/firmware/edd.c
@@ -192,6 +192,13 @@ edd_show_interface(struct edd_device *edev, char *buf)
 			p += scnprintf(p, left, " ");
 		}
 	}
+	/*
+	 * Phoenix EDD 3.0 reserves only one quad word for the
+	 * device path, so blank out the second quad word.
+	 */
+	if (info->params.device_path_info_length == 36)
+		info->params.device_path.unknown.reserved2 = 0;
+
 	if (!strncmp(info->params.interface_type, "ATAPI", 5)) {
 		p += scnprintf(p, left, "\tdevice: %u  lun: %u\n",
 			     info->params.device_path.atapi.device,
@@ -545,8 +552,12 @@ edd_has_edd30(struct edd_device *edev)
 	}
 
 
-	/* We support only T13 spec */
-	if (info->params.device_path_info_length != 44)
+	/*
+	 * Phoenix EDD 3.0 specifies this to be 36,
+	 * T-13 EDD 3.0 uses 44. So check for both.
+	 */
+	if (info->params.device_path_info_length != 36 &&
+	    info->params.device_path_info_length != 44)
 		return 0;
 
 	for (i = 30; i < info->params.device_path_info_length + 30; i++)

             reply	other threads:[~2012-05-16  6:51 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-16  6:51 Hannes Reinecke [this message]
2012-05-16  8:28 ` Gleb Natapov
  -- strict thread matches above, loose matches on Subject: below --
2012-05-15 11:04 Hannes Reinecke
2012-05-15 11:12 ` Gleb Natapov
2012-05-15 11:20   ` Hannes Reinecke
2012-05-15 11:59     ` Gleb Natapov
2012-05-15 12:53       ` Gleb Natapov
2012-05-15 13:49       ` Alan Cox
2012-05-15 14:12         ` Gleb Natapov
2012-05-15 14:18           ` Alan Cox
2012-05-15 14:21             ` Gleb Natapov
2012-05-15 14:36               ` Alan Cox
2012-05-15 14:48                 ` Gleb Natapov
2012-05-15 14:54                   ` Alan Cox
2012-05-15 15:00                     ` Gleb Natapov
2012-05-15 14:00       ` Alan Cox
2012-05-15 14:36         ` Gleb Natapov
2012-05-15 14:52           ` Alan Cox
2012-05-15 14:53             ` Gleb Natapov
2012-05-15 15:22               ` Alan Cox
2012-05-15 15:29                 ` Gleb Natapov
2012-05-15 15:41                   ` Alan Cox
2012-05-15 15:53                     ` Gleb Natapov
2012-05-15 15:14           ` Alan Cox
2012-05-15 15:31             ` Alan Cox
2012-05-15 15:46             ` Gleb Natapov
2012-05-15 17:17               ` H. Peter Anvin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1337151096-38511-1-git-send-email-hare@suse.de \
    --to=hare@suse.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gleb@redhat.com \
    --cc=hpa@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome