[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACdnJusL1Vj_rvhZY+0_KZkrk=fwnQcr1y+vxOBmUXa4xdHHsg@mail.gmail.com>
Date: Tue, 20 Feb 2018 21:22:29 +0000
From: Matthew Garrett <mjg59@...gle.com>
To: tony.luck@...el.com
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
joe.konno@...ux.intel.com, linux-efi <linux-efi@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
matthew.garrett@...ula.com, Jeremy Kerr <jk@...abs.org>,
ak@...ux.intel.com, pjones@...hat.com, luto@...nel.org,
James Bottomley <james.bottomley@...senpartnership.com>
Subject: Re: [PATCH 1/2] fs/efivarfs: restrict inode permissions
On Tue, Feb 20, 2018 at 1:18 PM Luck, Tony <tony.luck@...el.com> wrote:
> Does this rate an exception to the "don't break userspace" for a security
issue?
To be clear, when you say "security" is this in reference to it being a
denial of service, or are you worried about other interactions that may
cause wider security issues?
Powered by blists - more mailing lists