Re: [tip:x86/efi2] efivars: efivar_entry API
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [tip:x86/efi2] efivars: efivar_entry API
- From: Matt Fleming <matt.fleming@xxxxxxxxx>
- Date: Tue, 30 Apr 2013 12:27:31 +0100
- Cc: "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, "mingo@xxxxxxxxxx" <mingo@xxxxxxxxxx>, "hpa@xxxxxxxxx" <hpa@xxxxxxxxx>, "mjg59@xxxxxxxxxxxxx" <mjg59@xxxxxxxxxxxxx>, "tony.luck@xxxxxxxxx" <tony.luck@xxxxxxxxx>, "jk@xxxxxxxxxx" <jk@xxxxxxxxxx>, "teg@xxxxxxx" <teg@xxxxxxx>, "tglx@xxxxxxxxxxxxx" <tglx@xxxxxxxxxxxxx>, "mikew@xxxxxxxxxx" <mikew@xxxxxxxxxx>, "linux-tip-commits@xxxxxxxxxxxxxxx" <linux-tip-commits@xxxxxxxxxxxxxxx>
- In-reply-to: <A5ED84D3BB3A384992CBB9C77DEDA4D41AFD20E4@USINDEM103.corp.hds.com>
- Organization: Intel Corporation (UK) Ltd. - Registered No. 1134945 - Pipers Way, Swindon SN3 1RJ
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
On 26/04/13 16:43, Seiji Aguchi wrote:
> I tested pstore_read() as well.
> And /dev/pstore/dmesg-efi-X was empty....
>
> This must be __efivar_entry_get() instead of __efivar_entry_size().
> (We may have to introduce _efivar_entry_get_locked() to avoid deadlock.)
>
> I think it is a final bug report related to this new API patch.
Can you try the 'efi-for-tip-fixes' branch at,
git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi.git
and see if your problems are solved?
--
To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Index of Archives]
[Linux Stable Commits]
[Linux Stable Kernel]
[Linux Kernel]
[Linux USB Devel]
[Linux Video &Media]
[Linux Audio Users]
[Yosemite News]
[Linux SCSI]
