[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=whq+Kn-_LTvu8naGqtN5iK0c48L1mroyoGYuq_DgFEC7g@mail.gmail.com>
Date: Wed, 24 Jan 2024 09:27:34 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Kees Cook <keescook@...omium.org>
Cc: Kevin Locke <kevin@...inlocke.name>, John Johansen <john.johansen@...onical.com>,
Josh Triplett <josh@...htriplett.org>, Mateusz Guzik <mjguzik@...il.com>,
Al Viro <viro@...iv.linux.org.uk>, linux-mm@...ck.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-security-module@...r.kernel.org
Subject: Re: [6.8-rc1 Regression] Unable to exec apparmor_parser from virt-aa-helper
On Wed, 24 Jan 2024 at 09:21, Kees Cook <keescook@...omium.org> wrote:
>
> I opted to tie "current->in_execve" lifetime to bprm lifetime just to
> have a clean boundary (i.e. strictly in alloc/free_bprm()).
Honestly, the less uinnecessary churn that horrible flag causes, the better.
IOW, I think the goal here should be "minimal fix" followed by "remove
that horrendous thing".
Linus
Powered by blists - more mailing lists