All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Kees Cook <keescook@chromium.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Christoph Hellwig <hch@lst.de>,
	David Hildenbrand <david@redhat.com>,
	Hari Bathini <hbathini@linux.ibm.com>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Logan Gunthorpe <logang@deltatee.com>,
	Martin Oliveira <martin.oliveira@eideticom.com>,
	"Matthew Wilcox (Oracle)" <willy@infradead.org>,
	Mike Kravetz <mike.kravetz@oracle.com>,
	Minchan Kim <minchan@kernel.org>,
	Russell King <linux@armlinux.org.uk>,
	Stephen Rothwell <sfr@canb.auug.org.au>, Zi Yan <ziy@nvidia.com>
Subject: Re: [GIT PULL] hardening fixes for v5.18-rc1
Date: Thu, 31 Mar 2022 12:09:58 -0700	[thread overview]
Message-ID: <CAHk-=whPctCni+b7SDLtqnqW5qtiMnVqXQLZRA2iaQNStN7wXw@mail.gmail.com> (raw)
In-Reply-To: <202203311157.F7FA779@keescook>

On Thu, Mar 31, 2022 at 12:00 PM Kees Cook <keescook@chromium.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

WARNING: multiple messages have this Message-ID (diff)
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Kees Cook <keescook@chromium.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	 Christoph Hellwig <hch@lst.de>,
	David Hildenbrand <david@redhat.com>,
	Hari Bathini <hbathini@linux.ibm.com>,
	 Linux ARM <linux-arm-kernel@lists.infradead.org>,
	 Logan Gunthorpe <logang@deltatee.com>,
	Martin Oliveira <martin.oliveira@eideticom.com>,
	 "Matthew Wilcox (Oracle)" <willy@infradead.org>,
	Mike Kravetz <mike.kravetz@oracle.com>,
	 Minchan Kim <minchan@kernel.org>,
	Russell King <linux@armlinux.org.uk>,
	 Stephen Rothwell <sfr@canb.auug.org.au>, Zi Yan <ziy@nvidia.com>
Subject: Re: [GIT PULL] hardening fixes for v5.18-rc1
Date: Thu, 31 Mar 2022 12:09:58 -0700	[thread overview]
Message-ID: <CAHk-=whPctCni+b7SDLtqnqW5qtiMnVqXQLZRA2iaQNStN7wXw@mail.gmail.com> (raw)
In-Reply-To: <202203311157.F7FA779@keescook>

On Thu, Mar 31, 2022 at 12:00 PM Kees Cook <keescook@chromium.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

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-03-31 19:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-31 18:35 [GIT PULL] hardening fixes for v5.18-rc1 Kees Cook
2022-03-31 18:35 ` Kees Cook
2022-03-31 18:46 ` Russell King (Oracle)
2022-03-31 18:46   ` Russell King (Oracle)
2022-03-31 18:57   ` Kees Cook
2022-03-31 18:57     ` Kees Cook
2022-03-31 18:49 ` Linus Torvalds
2022-03-31 18:49   ` Linus Torvalds
2022-03-31 19:00   ` Kees Cook
2022-03-31 19:00     ` Kees Cook
2022-03-31 19:09     ` Linus Torvalds [this message]
2022-03-31 19:09       ` Linus Torvalds
2022-03-31 19:12 ` pr-tracker-bot
2022-03-31 19:12   ` pr-tracker-bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHk-=whPctCni+b7SDLtqnqW5qtiMnVqXQLZRA2iaQNStN7wXw@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=hbathini@linux.ibm.com \
    --cc=hch@lst.de \
    --cc=keescook@chromium.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=logang@deltatee.com \
    --cc=martin.oliveira@eideticom.com \
    --cc=mike.kravetz@oracle.com \
    --cc=minchan@kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=willy@infradead.org \
    --cc=ziy@nvidia.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.