3.2.46-rc1 review patch.  If anyone has any objections, please let me know.

------------------

From: Richard Weinberger <rich...@nod.at>

commit 7791c8423f1f7f4dad94e753bae67461d5b80be8 upstream.

Some EFI implementations return always a MaximumVariableSize of 0,
check against max_size only if it is non-zero.
My Intel DQ67SW desktop board has such an implementation.

Signed-off-by: Richard Weinberger <rich...@nod.at>
Signed-off-by: Matt Fleming <matt.flem...@intel.com>
Signed-off-by: Ben Hutchings <b...@decadent.org.uk>
---
 arch/x86/platform/efi/efi.c |    7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

--- a/arch/x86/platform/efi/efi.c
+++ b/arch/x86/platform/efi/efi.c
@@ -834,7 +834,12 @@ efi_status_t efi_query_variable_store(u3
        if (status != EFI_SUCCESS)
                return status;
 
-       if (!storage_size || size > remaining_size || size > max_size ||
+       if (!max_size && remaining_size > size)
+               printk_once(KERN_ERR FW_BUG "Broken EFI implementation"
+                           " is returning MaxVariableSize=0\n");
+
+       if (!storage_size || size > remaining_size ||
+           (max_size && size > max_size) ||
            (remaining_size - size) < (storage_size / 2))
                return EFI_OUT_OF_RESOURCES;
 

--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to