On 01/29/2013 01:25 PM, Matthew Garrett wrote:
On Tue, Jan 29, 2013 at 01:17:10PM +0800, Lingzhu Xiang wrote:
On 01/29/2013 12:44 PM, Matthew Garrett wrote:
[root@qemu-ovmf efivars]# touch BootOrder-8BE4DF61-93CA-11D2-AA0D-00E098032B8C
Ha ok. Other than the change in name over unmount, does this one cause
any problems?
This demonstrates how to create two files with the same name in efivarfs.
[root@qemu-ovmf efivars]# ll BootOrder*
-rw-r--r--. 1 root root 12 Jan 25 14:56
BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r--. 1 root root 12 Jan 25 14:56
BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c
Huh. The firmware permits two variables with the same GUID in different
cases?
The two files points to the same variable.
So I create a file with upper case GUID string, but the upper and lower case
are parsed to be the same binary value and saved separately in sysfs. During
remount, the binary GUID is formatted to lower case, so the upper and lower
case sysfs entries come back to efivarfs with the same name.
This is just trying to explore the impact of not having GUID validation for
filename. Not something new.
--
To unsubscribe from this list: send the line "unsubscribe linux-efi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
