linux-kernel - [GIT PULL] EFI changes for v3.9-rc2

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <1362583718.15011.89.camel@mfleming-mobl1.ger.corp.intel.com>
Date:	Wed, 06 Mar 2013 15:28:38 +0000
From:	Matt Fleming <matt@...sole-pimps.org>
To:	"H. Peter Anvin" <hpa@...ux.intel.com>,
	Ingo Molnar <mingo@...nel.org>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-efi <linux-efi@...r.kernel.org>
Subject: [GIT PULL] EFI changes for v3.9-rc2

Hi guys,

The following changes since commit feff5dc4f98330d8152b521acc2e18c16712e6c8:

  efivarfs: return accurate error code in efivarfs_fill_super() (2013-03-06 14:46:30 +0000)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi.git tags/efi-for-3.9-rc2

for you to fetch changes up to feff5dc4f98330d8152b521acc2e18c16712e6c8:

  efivarfs: return accurate error code in efivarfs_fill_super() (2013-03-06 14:46:30 +0000)

----------------------------------------------------------------
EFI changes for v3.9-rc2,

  * Make the EFI variable code more paranoid about running out of
    space in NVRAM, since this is the root cause of the recent issue
    where machines refuse to boot - from Matthew Garrett.

  * Some efivarfs patches that fix regressions introduced in v3.9-rc1.

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

-- 
Matt Fleming, Intel Open Source Technology Center

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