[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=whPctCni+b7SDLtqnqW5qtiMnVqXQLZRA2iaQNStN7wXw@mail.gmail.com>
Date: Thu, 31 Mar 2022 12:09:58 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Kees Cook <keescook@...omium.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Christoph Hellwig <hch@....de>,
David Hildenbrand <david@...hat.com>,
Hari Bathini <hbathini@...ux.ibm.com>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
Logan Gunthorpe <logang@...tatee.com>,
Martin Oliveira <martin.oliveira@...eticom.com>,
"Matthew Wilcox (Oracle)" <willy@...radead.org>,
Mike Kravetz <mike.kravetz@...cle.com>,
Minchan Kim <minchan@...nel.org>,
Russell King <linux@...linux.org.uk>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Zi Yan <ziy@...dia.com>
Subject: Re: [GIT PULL] hardening fixes for v5.18-rc1
On Thu, Mar 31, 2022 at 12:00 PM Kees Cook <keescook@...omium.org> wrote:
>
> I can do that, but it seemed like more work for folks: a larger diff to
> look at, and a rebase for Matthew or me. It's not MUCH more work, but
> given the timing of the merge window, I wanted to have a minimal diff.
Stuff that just does obvious code removal may _look_ big, but I
actually think it's conceptually a smaller patch than the subtle one
that just made the code impossible to enable.
Marking something broken implies that maybe we'll be able to fix it.
This seems to be more of a "let's just get rid of it".
Linus
Powered by blists - more mailing lists