From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Kees Cook <kees@kernel.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
linux-kernel@vger.kernel.org, Eric Biggers <ebiggers@kernel.org>,
Ingo Saitz <ingo@hannover.ccc.de>,
kernel test robot <oliver.sang@intel.com>,
Marco Elver <elver@google.com>,
Nathan Chancellor <nathan@kernel.org>,
Thiago Jung Bauermann <thiago.bauermann@linaro.org>
Subject: Re: [GIT PULL] hardening fixes for v6.16-rc1
Date: Sat, 31 May 2025 22:36:41 +0100 [thread overview]
Message-ID: <20250531213641.GE3574388@ZenIV> (raw)
In-Reply-To: <CAHk-=wj4a_CvL6-=8gobwScstu-gJpX4XbX__hvcE=e9zaQ_9A@mail.gmail.com>
On Sat, May 31, 2025 at 11:20:20AM -0700, Linus Torvalds wrote:
> On Sat, 31 May 2025 at 08:00, Kees Cook <kees@kernel.org> wrote:
> >
> > Please pull this small handful of hardening fixes for v6.16-rc1.
>
> WTF, Kees?
>
> You seem to have actively maliciously modified your tree completely.
>
> There are completely crazy commits in there that are entirely fake.
>
> You have this: f8b59a0f90a2 Merge tag 'driver-core-6.16-rc1' of
> git://git.kernel.org/pub/scm/linux/kernel/git/driver-core/driver-core
>
> which *claims* to be from me, and committed by me, but is very much
> not. It's some garbage you have entirely made up.
>
> Yes, there is a real commit like that, but it's has the SHA1 ID of
> 9d230d500b0e.
Interesting - looks like a large part of commit graph had been mirrored
with mergetag parts filed off; actual tree objects appear to match...
next prev parent reply other threads:[~2025-05-31 21:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-31 15:00 [GIT PULL] hardening fixes for v6.16-rc1 Kees Cook
2025-05-31 18:20 ` Linus Torvalds
2025-05-31 19:21 ` Konstantin Ryabitsev
2025-05-31 19:57 ` Konstantin Ryabitsev
2025-05-31 21:36 ` Al Viro [this message]
2025-06-01 1:06 ` Kees Cook
2025-06-01 2:22 ` Stephen Rothwell
2025-06-01 2:35 ` Linus Torvalds
2025-06-01 5:42 ` Kees Cook
2025-06-01 7:42 ` Kees Cook
2025-06-01 14:40 ` Konstantin Ryabitsev
2025-06-01 15:38 ` Kees Cook
2025-06-01 17:58 ` Konstantin Ryabitsev
2025-06-01 18:56 ` Kees Cook
2025-06-03 12:55 ` Vlastimil Babka
2025-06-01 17:12 ` Linus Torvalds
2025-06-01 17:49 ` Konstantin Ryabitsev
2025-06-01 18:24 ` Linus Torvalds
2025-06-03 12:42 ` Christian Brauner
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=20250531213641.GE3574388@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=ebiggers@kernel.org \
--cc=elver@google.com \
--cc=ingo@hannover.ccc.de \
--cc=kees@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=oliver.sang@intel.com \
--cc=thiago.bauermann@linaro.org \
--cc=torvalds@linux-foundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox